Check Wait Stats in 45 Seconds. From Symptoms to Root Clause. The "45 Seconds DBA Series" – What Real DBAs Check First | Part 9


Check Wait Stats in 45 Seconds

From Symptoms to Root Cause. The "45 Seconds DBA Series" – Part 9 🥇

Before we dive into today's topic, if you missed my previous post you can take a look at A recap of my April 2026 posts.

👉 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.

If you aren't looking at Wait Stats, you aren't tuning performance—you're guessing. In this post, I will show you how to cut through the noise and identify exactly what is throttling your SQL Server in under 45 seconds.

✔️ Wait Stats = The Truth: They tell you why a thread is not moving. 🛠️

✔️ Resource vs. Signal: Distinguish between waiting for a disk (Resource) and waiting for a CPU (Signal). 📦

✔️ Filter the Noise: Real DBAs ignore background tasks like Lazy Writer and Checkpoint to focus on user impact. 🚀

✔️ Baseline is King: Accumulative stats mean nothing without knowing what's "normal" for your workload. ✔️

Hi SQL SERVER Guys,

When a user complains that "the database is slow," the worst thing you can do is start changing indexes or adding RAM blindly. SQL Server is a "Wait-Based" engine. Every time a request can't proceed, it records exactly why it stopped. Whether it's waiting for a lock, a data page from disk, or a CPU scheduler, the answers are already there. Let's find the truth in 45 seconds...

What It Really Is: The Waiting Game

Every request in SQL Server goes through three states: Running, Runnable, and Suspended. Wait stats are generated when a thread moves into the Suspended state because it needs a resource (like a page lock) that isn't immediately available.

💣 The Problem:

Standard monitoring often gives you a "Top Waits" list that includes background noise. If you see LAZYWRITER_SLEEP or LOGMGR_QUEUE at the top, you might panic for no reason. These are benign. Real pressure comes from:

  • PAGEIOLATCH_XX: Your storage subsystem can't keep up with the I/O demand.
  • SOS_SCHEDULER_YIELD: Your queries are burning through their 4ms quantum and waiting for a CPU turn.
  • LCK_M_X: Blocking is killing your concurrency.

🧪 The 45-Second Diagnostic Query

This script excludes the "benign" waits and calculates the percentage of impact for each wait type. It’s the first script I run on any server I’m called to troubleshoot. 

-- 🔍 Global Wait Stats Diagnostic Query
WITH [Waits] AS (
    SELECT
        [wait_type],
        [wait_time_ms] / 1000.0 AS [WaitS],
        ([wait_time_ms] - [signal_wait_time_ms]) / 1000.0 AS [ResourceS],
        [signal_wait_time_ms] / 1000.0 AS [SignalS],
        [waiting_tasks_count] AS [WaitCount],
        100.0 * [wait_time_ms] / SUM([wait_time_ms]) OVER() AS [Percentage]
    FROM sys.dm_os_wait_stats
    WHERE [wait_type] NOT IN (
        'CLR_SEMAPHORE', 'LAZYWRITER_SLEEP', 'OLD_RESOURCES_CHECK',
        'SQLTRACE_BUFFER_FLUSH', 'SLEEP_TASK', 'CHECKPOINT_QUEUE',
        'XE_TIMER_EVENT', 'REQUEST_FOR_DEADLOCK_SEARCH')
)
SELECT TOP 10 * FROM [Waits]
WHERE [WaitS] > 0
ORDER BY [WaitS] DESC;

For detailed definitions of each wait type, refer to the official Microsoft Documentation.

🚀 My REAL Strategy

In my 25 years of experience, I’ve seen DBAs make the mistake of clearing wait stats (DBCC SQLPERF) just to "see what's happening now." Don't do it. You lose your historical context.

Instead, follow my "Signal vs Resource" rule:

  • 🧠 High Signal Waits (>20%): This is a clear indicator of CPU pressure. Your threads are ready to run but the CPU is too busy to pick them up. Don't buy more cores; optimize your code to reduce context switching.
  • 🧠 High Resource Waits: Focus on the specific resource. If PAGEIOLATCH_SH is your top wait, check your Top Logical Reads. High I/O waits are often just poor indexing forcing massive scans into memory.
  • 🧠 CXPACKET is a Symptom: If you see CXPACKET, don't just disable parallelism. Check for CXCONSUMER. If CXPACKET is high alongside LATCH_XX, you likely have skewed data distribution in your parallel threads.

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!

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