Check SQL Server Cardinality Estimation Issues in 45 Seconds. The "45 Seconds DBA Series". Part 12

Before we dive into today's topic, if you missed my previous post you can take a look at Check Execution Plans in 45 Seconds.

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

Check SQL Server Cardinality Estimation Issues in 45 Seconds

Execution Engine Deep Dive | Part 12

In this post, I will show you how to identify the silent killer of performance: the "Estimate vs Actual" row gap. Mastering Cardinality Estimation is the difference between a sub-second response and a server-wide timeout.

🧠 TL;DR BOX

✔️ Cardinality Estimation (CE) is the Optimizer's prediction of how many rows a query will process.
✔️ A massive discrepancy between Estimated and Actual rows leads to sub-optimal join choices and memory grant spills.
✔️ Primary culprits: Outdated statistics, table variables, and complex non-SARGable predicates.
✔️ Diagnosis takes less than 45 seconds using the plan cache or Execution Plan comparison.

Hi SQL SERVER Guys and Gals,

We all know how important it is to make every second count when managing SQL Server environments. When the Query Optimizer makes a decision, it relies on a "guess" called Cardinality Estimation. If that guess is wrong, the entire execution plan is built on a lie. Let's dive into how you can spot these lies instantly.

🔍 DIAGNOSIS: The Cardinality Skew

🧠 What it really is: Cardinality Estimation is the mathematical model SQL Server uses to predict the number of rows returned by each operator. The Optimizer uses Statistics (histograms) to make these calls. If the stats are stale or the query is too complex (e.g., multiple joins with skewed data), the CE fails.

💣 The Problem: When SQL Server expects 1 row but gets 1,000,000:

  • It chooses a Nested Loop Join instead of a Hash Join.
  • It requests a tiny Memory Grant, causing a massive spill to TempDB.
  • CPU usage spikes as the engine struggles with an inefficient plan.

🧪 QUERY: Identify Skewed Plans in Cache

Use this script to find the top 20 queries where the Optimizer's "guess" was significantly different from reality.

-- 🔍 CE Skew Diagnostic Query
SELECT TOP 20
    st.text AS [Query Text],
    qp.query_plan AS [Plan],
    qs.total_worker_time / qs.execution_count AS [Avg CPU],
    CAST(qs.max_rows AS FLOAT) / NULLIF(qs.max_grant_kb,0) AS [Row Density],
    stat.last_execution_time,
    -- Comparing Max Rows vs Average Rows to find variance
    qs.max_rows,
    qs.min_rows,
    qs.total_rows / qs.execution_count AS [Avg Rows]
FROM sys.dm_exec_query_stats qs
CROSS APPLY sys.dm_exec_sql_text(qs.sql_handle) st
CROSS APPLY sys.dm_exec_query_plan(qs.plan_handle) qp
ORDER BY [Avg Rows] DESC;

🚀 FIX: Closing the Gap

If you identify a CE issue, you have three immediate paths to resolution:

  • ✔️ Update Statistics: Run UPDATE STATISTICS [TableName] WITH FULLSCAN;. Often, a 10% sample isn't enough for skewed data.
  • ✔️ Replace Table Variables: Table variables don't have statistics (mostly). Use #TempTables so the Optimizer can see the data distribution before choosing the plan.
  • ✔️ Query Hints: In SQL 2014+, you can use OPTION (USE HINT('FORCE_LEGACY_CARDINALITY_ESTIMATION')) if the new model is producing regressions on legacy code.

🚀 My REAL Strategy

In my 25 years of experience, the biggest mistake DBAs make is blaming the code when the problem is the Metadata. If you see a plan where a Hash Match operator is spilling to disk, don't just add an index. Check the CE. If the estimate was 100 rows and it processed 10 million, no index in the world will fix that memory grant deficit. Fix the stats first, then look at the T-SQL.

📊 TAKEAWAY

Cardinality estimation is the heart of the Execution Engine. Always compare Estimated vs. Actual. If they are off by more than 10x, you aren't tuning a query; you're fighting a broken model. Correct the model, and the performance will follow.

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