Check CPU Pressure in 45 Seconds. The "45 Seconds DBA Series" – What Real DBAs Check First | Part 3 🥇

Before we dive into today's topic, if you missed my previous post you can take a look at Check Tempdb Health In 45 Seconds: Part 2 of the 45 Seconds DBA Series .

👉 If you found this deep-dive helpful, feel free to check out the ads—your support helps me keep creating high-quality SQL Server content for the community.

Stop chasing 100% CPU ghosts. In this post, I’ll show you how to distinguish between a "busy" CPU and a "choked" CPU in under 45 seconds so you can stop wasting money on unnecessary hardware upgrades!

⚡ TL;DR

✔️ High CPU % is a symptom, not a diagnosis. It doesn't always mean the CPU is the bottleneck. 🛠️
✔️ Check Runnable Tasks: If runnable_tasks_count is consistently > 0, your threads are waiting for a turn. 📦
✔️ Signal Waits: A high percentage of signal waits ( > 20%) confirms real CPU pressure. 🚀
✔️ Actionable Fixes: 90% of CPU pressure is solved by better indexing, not more cores. ✔️

Hi SQL SERVER Guys,

We all know how important it is to make every second count when managing SQL Server environments. When a server hits 95% CPU, most admins panic and immediately call for more vCPUs. But today we will show that High CPU is often a hostage situation, not a capacity problem. Keep in mind: If your queries are poorly written, SQL Server will burn cycles just to keep up. Let's find the truth in 45 seconds...

What It Really Is: Busy vs. Backlogged

Standard monitoring tools show you the utilization, but they rarely show you the queue. SQL Server uses "Cooperative Scheduling", this mean that a task runs for its quantum (4ms) and then yields.

💣 The Problem

If a task wants to run but there is no available scheduler, it sits in the RUNNABLE queue. This is the "waiting room" for the CPU. If this queue is long, you have real pressure.

We have the following two fundamentals DMVs:

  • sys.dm_os_schedulers: This is your primary investigative tool to see the queue.
  • Signal Waits: The difference between when a resource was ready and when the CPU actually picked up the task.

🧪 The 45-Second Investigation Script

Run this query to immediately see if your CPUs are actually struggling to keep up with the workload demand:

SELECT 
    scheduler_id, 
    cpu_id, 
    [status], 
    is_online, 
    runnable_tasks_count, -- Tasks waiting for CPU
    current_workers_count, 
    load_factor
FROM sys.dm_os_schedulers
WHERE [status] = 'VISIBLE ONLINE';

-- If runnable_tasks_count is > 0 consistently, 
-- your CPU is the bottleneck.

If runnable_tasks_count is high across all schedulers, your queries are fighting for CPU time. If it's 0 but CPU is 100%, your queries are simply "heavy" but not necessarily queuing yet.

🚀 My REAL Strategy

In my experience, CPU pressure is almost always an Indexing or SARGability problem in disguise. Before you scale up your Azure instance or buy more licenses:

  1. Kill the Scans: Check for "Index Scan" operators in your most frequent queries. A scan consumes massive CPU compared to a Seek.
  2. Check for Implicit Conversions: When SQL has to convert data types on the fly to join tables, it eats CPU for breakfast.
  3. Validate Signal Waits: Use sys.dm_os_wait_stats. If Signal Waits are more than 20% of your total wait time, it confirms the CPU can't keep up with the task switching.

Rule of thumb: Don't feed the beast with more cores until you've optimized the code that's starving it.

Related Posts

📢 Support the Blog: Did you find this deep-dive helpful? The ads you see here are selected to reflect your interests. If a partner's offer catches your eye, give it a look! Your engagement helps me continue publishing premium SQL Server content for the community.

Biondi Luca @2026 - Sharing over 25 years of Gained Knowledge for Passion. Share if you like my posts! 

Today I am also on substack here: QueryForge

Comments

Post a Comment

I Post più popolari

Speaking to Sql Server, sniffing the TDS protocol

Image
Hello friends!  If yesterday you read my post and found it definitely boring (for the topic of course and not for how it was written to the author 😁) well today I promise you that the topic will be much more interesting! Let's talk about Sniffing , let's talk about going to see what happens when we "log in" or when we send a Query to SQL Server.  We will do this by taking a look to the little known tabular data stream (TDS) protocol built on top of the TCP/IP protocol. Ready! The TDS protocol What is the Tabular data stream (TDS) protocol?  The TDS is the protocol used by the SQL Server client Net-Library to communicates with SQL Server . TDS is specific to SQL Server and it is a low-level protocol that specifies both commands and data in a specific arrangement.  TDS encapsulate the TCP/IP protocol. Sniffing TDS packets you can read from the network the requests that your application do to the SQL Server and read the answer .   How to Sniff data from the ne...
Read more

SQL Server, find text in a Trigger, Stored Procedures, View and Function. Two ways and what ways is better

Image
Hi guys, Welcome back! Today a light post about a question that has been asked to me several times. The question is: how to  search for text inside a trigger or a stored procedure ? We have two different ways. A first way using a system view called syscomments: SELECT obj.xtype, text , * FROM sysobjects obj JOIN syscomments com on obj.id = com.id WHERE TEXT like '%text_that_i_am_searching_for%' A second way using a system view called sql_module: SELECT o. name AS Object_Name, o. type_desc , m. definition FROM sys.sql_modules m JOIN sys.objects o ON m. object_id = o. object_id WHERE m. definition Like '%text_that_i_am_searching_for%' ;   Another question is? What differences do we have in using one way instead of the other? Which solution is better? You have to consider that the system view sys.syscomment is obsolete and will be removed sooner or later. So don't use it in production enviroiments. The sys.sql_m...
Read more

SQL Server, Avoid that damn Table Spool!

Image
Hi guys, Welcome back for another post! A light one inspired from what i do during my work: many times I optimize queries rewriting them or adding index and i like it very much! Sometimes you need to use a little imagination, but everything you learn ... sooner or later it will come in handy! Enjoy the reading mates! Avoid the Table Spool, when you can A few days ago I came across a query whose execution time was very high ... or so it was for the client complaining about the problem. Before recreating it, let's create the structures and fill the tables with some data Create table PriceList (Id int identity (1,1) primary Key ,Code Varchar (20)) Insert into PriceList (code) select top 1000 right( '0000' + cast ( row_number () over ( order by id) as varchar (4)),4) from artico Insert into PriceList (code) select top 4000 right( '1000' + cast ( row_number () over ( order by id) as varchar (4)),4) from artico Create table OrdersList (Id int identity...
Read more