SQL Server performance problems may originate in CPU pressure, memory constraints, disk latency, network delays, inefficient queries, or blocking. Windows monitoring tools help separate symptoms from their causes.
Start with a baseline
Collect counters when the server is healthy, then compare them with periods when users report slow response. Record collection intervals, workload characteristics, and server configuration.
Useful observations
Task Manager gives a quick summary; Resource Monitor reveals active disk, network, CPU, and memory use; Performance Monitor (perfmon) records counters over time. SQL Server adds its own performance-counter categories, although available counters vary by version and installation.
Correlate with SQL Server
Use Query Store, wait statistics, execution plans, and selected dynamic management views to connect a Windows bottleneck with specific queries. A high CPU reading alone does not establish which SQL statement caused it.
A practical workflow
Reproduce a slow report; measure duration and logical reads; inspect server CPU and disk activity; examine the actual execution plan; verify blocking and waits; make one controlled change; measure again.
Cautions
Do not change memory or parallelism settings based on one snapshot. Historical SQL Server Profiler tutorials may still be informative, but Extended Events and Query Store are generally more appropriate modern starting points.
About this article: This AI-generated educational rewrite was prepared from an existing Open Education article, with new explanations and illustrative examples where helpful. Read the earlier article (post 75926). The new text may be freely copied, edited, and reused with or without attribution to this site. Third-party material, brand names, and linked resources retain their own rights. AI can make mistakes: verify syntax, version support, security practices, and outcomes against official documentation before use, especially in production.
