Data Monitoring / SQL Server Query Performance
SQL Server: High total CPU versus slow single calls
A very fast query consumes most database CPU because it executes often. Compare total CPU contribution, per-execution CPU and call frequency.
Environment and inputs: SQL Server 2019–2025 where the referenced feature is supported; Query Store and diagnostic collection require appropriate configuration and permissions. Azure SQL behavior can differ.
Failure scenario
A very fast query consumes most database CPU because it executes often. Confirm the cause before choosing a fix.
Evidence to collect
Compare total CPU contribution, per-execution CPU and call frequency. Record the time, affected scope and a healthy comparison interval.
Fix the confirmed cause
Reduce excessive calls or repeated work rather than optimizing only the slowest single execution. Write the expected result first. Change one relevant setting at a time.
Check the result and hand over
Repeat the check for high total cpu versus slow single calls using the same scope and a representative interval. Check that the symptom is resolved, expected records are present and downstream results are correct. If coverage, correctness or latency worsens, restore the recorded configuration through the agreed rollback process.
Scope and precautions
Prefer read-only access and limit queries to the relevant period or dataset. This example has not been tested on your systems. Test changes in an approved environment. Keep credentials and sensitive data out of shared evidence.