The SQL Server CPU page shows CPU-related monitoring data for a SQL Server instance. Use it to understand CPU pressure, workload spikes, and whether query tuning or host investigation is needed.
When To Use This Page
- CPU alerts are firing.
- Users report slow response times.
- Activity shows high CPU requests.
- Cached SQL shows expensive CPU queries.
- You need to correlate CPU pressure with waits and workload.
Workflow
- Open CPU for the SQL Server.
- Review recent CPU trends.
- Compare spikes with Activity.
- Sort Cached SQL by CPU.
- Check Waits for scheduler or parallelism symptoms.
How To Investigate SQL Server CPU Pressure
CPU pressure can come from a few expensive queries, many small queries, parallelism, compilation, inefficient plans, or work outside SQL Server on the host. Start by matching the CPU spike to a time window. Then use SQL Server Activity to see live workload and Cached SQL or SQL Server Query Store to find statements with high CPU cost.
Do not assume that more CPU is the only fix. Query tuning, better indexes, plan regression analysis, parameter sensitivity review, and application batching can reduce CPU without changing hardware. If host OS metrics are available, also check whether another process is consuming CPU on the server.
CPU should be compared with waits. If waits show storage or locking as the dominant delay, CPU may be a symptom rather than the bottleneck.
SQL Server CPU FAQ
Should I tune the highest CPU query first?
Start with the highest total business impact. A frequent medium-cost query can matter more than a rare expensive one.
Can high CPU be caused by missing indexes?
Yes. Missing or inefficient indexes can force scans, extra joins, and expensive plan choices.
Where do I check host CPU?
Configure Host OS Login where appropriate so Mini DBA can collect host-level metrics. For Windows SQL Server hosts, use Enable WMI For SQL Server Monitoring to allow CPU core and process visibility.