Windows power plans and SQL Server CPU behaviour
Balanced power plans can park cores and surprise latency SLAs. Why host configuration still belongs in a database health review.
Not every SQL problem lives inside T-SQL. Host configuration — power plans, antivirus exclusions, storage drivers — still decides whether CPUs show up when the optimiser asks.
Common finding
The OS runs a Balanced power plan. Cores park. Latency spikes under bursty load. Everyone blames “SQL.”
What we check alongside
- High performance power plan on dedicated SQL hosts (or equivalent BIOS settings)
- CPU scheduling symptoms vs true query CPU demand
- Competing workloads on the same VM host
- Hypervisor oversubscription stories
Shared responsibility
DBAs and infrastructure teams share this surface. Health checks that ignore the host miss easy wins; infrastructure changes without query evidence also miss. We connect both sides with measurements.
Need hands-on SQL Server help?
Allay Data Solutions offers maintenance, tuning, and assessments from Port Elizabeth, South Africa.