This is the second of two connected posts on SQL Server CPU.
In this post, Kevin Kline focuses on the moving parts that turn into real incidents: SQL Server wait statistics, thread scheduling pressure, troubleshooting workflow, and how observability tools shorten the path from symptom to root cause. In Part 1, we looked at how SQL Server uses CPU, why high CPU usage in SQL Server is often misunderstood, and which configuration habits help create a more stable, high-performance environment.
This is the first of two connected posts on database performance tuning. In this post, Kevin Kline explains how SQL Server uses CPU, why high SQL Server CPU usage is often misunderstood, and which configuration habits help build a more stable, high-performance environment.
In the second post, we look at SQL Server wait statistics, scheduler pressure, troubleshooting workflow, and how to arrive at root cause faster.
SQLPerformance is back. This piece explores why the site still matters, what changed during the transition from SentryOne to SolarWinds, and how the site fits into today’s broader database community.
It also looks at the role SQLPerformance can continue to play as database teams face more complexity, more observability demands, and more pressure to move from reactive work to faster, better-informed decisions.
In this post, Eoin Keenan breaks down the SolarWinds Database Portfolio May 2026 Product Update and explains what the latest product release means for database teams.