copilot-instructions database-configuration-operations.instructions.md

Database Configuration and Operations Baseline

• Use this instruction when configuring runtime database access, connection settings, failover, or operational database policies.
• Prioritize secure-by-default settings, deterministic performance, and recoverability under real production load.

Environment and Configuration Source of Truth

• Keep database settings environment-specific and externalized (local, staging, production).
• Maintain a single typed configuration contract for each service; avoid ad-hoc config reads.
• Keep configuration keys stable across environments; only values change.
• Do not hardcode connection strings, passwords, certificates, or provider credentials.

Connection String and Secret Management

• Store credentials in managed secret stores; inject at runtime with least privilege.
• Enforce TLS/SSL in all non-local environments.
• Disable trust-on-first-use defaults; require explicit certificate validation where supported.
• Include application/service name in connection metadata for traceability.
• Separate read/write/admin credentials and rotate each on independent schedules.

Provider Baselines

• SQL Server baseline:
  • Encrypt=True
  • TrustServerCertificate=False
  • MultiSubnetFailover=True when applicable
  • Explicit Connect Timeout and command timeout defaults
• PostgreSQL baseline:
  • SSL Mode=Require (or stronger policy)
  • Trust Server Certificate=false outside controlled local development
  • Explicit Timeout, Command Timeout, and Keepalive
• MySQL baseline:
  • SslMode=Required
  • Explicit ConnectionTimeout and DefaultCommandTimeout
  • Explicit character set/collation strategy where relevant

Pooling and Timeout Policy

• Enable pooling with explicit min/max bounds; never rely on unknown runtime defaults in production.
• Define MinPoolSize and MaxPoolSize per service profile and expected concurrency.
• Set command timeout by endpoint/query class, not a single global extreme value.
• Bound concurrent database calls at application layer to avoid pool starvation.
• Fail fast on acquisition timeouts and surface clear diagnostics.