Check Execution Plans in 45 Seconds. Execution Engine. The "45 Seconds DBA Series" | Part 11

Before we dive into today's topic, if you missed my previous post you can take a look at SQL Server 2025 Built-in Chunking and Vector Support AI Functions, the Brutal Truth. From SQL to AI series, Part 1.

👉 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 Execution Plans in 45 Seconds

Master the Execution Engine: The "45 Seconds DBA Series" | Part 11

Stop guessing why your queries are slow. In 45 seconds, I’ll show you how to intercept the Query Optimizer's roadmap and pinpoint bottlenecks before they kill your production environment!

🧠 TL;DR

✔️ Use DMVs to extract XML plans for currently running requests instantly 🛠️
✔️ Identify Index Scans vs. Seeks to verify SARGability 🔍
✔️ Spot "Fat Arrows" and Cardinality Misestimations in the Execution Engine 🚀
✔️ Detect Missing Index warnings directly from the XML plan metadata ✔️

Hi SQL SERVER Guys and Gals,

We all know that time is the most expensive resource in a high-concurrency environment. When a query spikes CPU, you don't have 10 minutes to set up a Trace or Extended Events. You need to see the Execution Plan right now. Understanding the Execution Engine's choices is the difference between a Junior DBA and a Performance Expert. Let's get moving!

🔍 DIAGNOSIS: What It Really Is

An Execution Plan is the binary representation of how the SQL Server Execution Engine will physically navigate your data. It’s not just a pretty picture in SSMS; it’s a detailed XML structure containing costs, warnings, and actual vs. estimated row counts.

  • 💣 Implicit Conversions: Look for warnings on the Select operator.
  • 💣 Residual Predicates: When a Seek is actually acting like a Scan.
  • 💣 Memory Grants: Excessive grants causing resource semaphore waits.

🧪 QUERY: The "Wow" Extraction Script

Forget clicking menus. Use this T-SQL to grab the Live Execution Plan of any query currently hammering your CPU. This is the fastest way to see what's happening under the hood.

-- 🔍 Live Execution Engine Diagnostic
-- Extracts the XML Plan and SQL Text for active requests
SELECT 
    r.session_id,
    r.start_time,
    r.total_elapsed_time,
    st.text AS [Query Text],
    qp.query_plan AS [Interactive Execution Plan], -- Click this in SSMS!
    r.status,
    r.wait_type,
    r.cpu_time,
    r.logical_reads
FROM sys.dm_exec_requests r
CROSS APPLY sys.dm_exec_sql_text(r.sql_handle) st
CROSS APPLY sys.dm_exec_query_plan(r.plan_handle) qp
WHERE r.session_id <> @@SPID 
  AND r.status NOT IN ('background', 'sleeping');

🚀 My REAL Strategy

In my 25 years of experience, the "Missing Index" warning is often a trap. Don't blindly apply it. Look at the Index Scan operator first. If the engine is scanning a million rows to return ten, check if your WHERE clause is SARGable. A simple CAST or a function wrapping a column can force a scan even if the perfect index exists.

Always compare Actual Number of Rows vs Estimated Number of Rows. If the difference is huge, your statistics are stale or you've hit a cardinality estimator bug. That is where the real performance gains are hidden.

📊 TAKEAWAY

  • 🚀 Action: Always use SET STATISTICS XML ON in dev to catch warnings early.
  • 🧠 Concept: The Optimizer chooses the "Good Enough" plan, not always the perfect one.
  • ⚡ Insight: Parallelism (CXPACKET) isn't the problem; it's the symptom of a high-cost plan.

Official References:

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