Check SQL Server Missing Indexes (and Why They Lie) in 45 Seconds. The "45 Seconds DBA Series". Part 13

Before we dive into today's topic, if you missed my previous post you can take a look at Check Cardinality Estimation Issues in 45 Seconds. Execution Engine | Part 12.

👉 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 Missing Indexes (and Why They Lie) in 45 Seconds

Execution Engine Deep Dive | Part 13

In this post, you will learn how to extract the highest impact missing indexes from the plan cache and why blindly applying "green text" suggestions can destroy your server's write performance.

🧠 TL;DR BOX

✔️ Use sys.dm_db_missing_index_details to identify gaps the Optimizer noticed during compilation.
✔️ The "Missing Index" feature is a hint, not a command; it doesn't consider existing indexes or write overhead.
✔️ Never create overlapping indexes; consolidate suggestions into existing structures where possible.
✔️ Execution plan suggestions ignore filtered indexes and optimal column ordering.

Hi SQL SERVER Guys and Gals,

We all know how important it is to make every second count when managing SQL Server environments. Most DBAs see the "Missing Index" warning in an execution plan and immediately hit 'Create'. That is a rookie mistake. Today, I'll show you how to audit these suggestions properly and why the Engine sometimes "lies" about what it needs. Let's get to work!

🔍 DIAGNOSIS: The Missing Index Trap

🧠 What it really is: The SQL Server Query Optimizer has a built-in feature that identifies if a query could have performed better if a specific index existed. This data is stored in Dynamic Management Views (DMVs) and displayed as green text in SSMS.

💣 The Catch: The Missing Index feature is "blind" to several critical factors:

  • It doesn't consider write performance. Every index slows down INSERTs and UPDATEs.
  • It doesn't recognize overlapping indexes. It might suggest 10 indexes for the same table that could be solved by one properly designed composite index.
  • It has a limit of 40 columns and does not suggest filtered indexes or consider include column order.

🧪 QUERY: The 45-Second Audit

Don't look at plans one by one. Use this query to find the "Heavy Hitters" currently affecting your entire instance.

-- 🔍 High Impact Missing Index Diagnostic Query
SELECT TOP 20
    [Impact] = (avg_total_user_cost * avg_user_impact) * (user_seeks + user_scans),
    [Table] = [statement],
    [Equality_Columns] = equality_columns,
    [Inequality_Columns] = inequality_columns,
    [Included_Columns] = included_columns,
    [Last_User_Seek] = last_user_seek,
    [Create_Statement] = 'CREATE INDEX [IX_' + OBJECT_NAME(d.object_id) + '_' 
        + REPLACE(REPLACE(REPLACE(ISNULL(equality_columns,''),', ','_'),'[',''),']','') 
        + '] ON ' + [statement] 
        + ' (' + ISNULL(equality_columns,'') 
        + ISNULL(CASE WHEN equality_columns IS NOT NULL AND inequality_columns IS NOT NULL THEN ',' END,'') 
        + ISNULL(inequality_columns,'') + ')' 
        + ISNULL(' INCLUDE (' + included_columns + ')','')
FROM sys.dm_db_missing_index_group_stats s
JOIN sys.dm_db_missing_index_groups g ON s.group_handle = g.index_group_handle
JOIN sys.dm_db_missing_index_details d ON g.index_handle = d.index_handle
WHERE [statement] NOT LIKE '%[sys]%'
ORDER BY [Impact] DESC;

🚀 FIX: The Consolidation Method

When you find a "missing index" suggestion, follow these three steps before running the script:

  • ✔️ Check for Overlaps: Use sp_helpindex to see if the table already has an index with the same leading column. If so, simply add the "Included" columns to the existing index.
  • ✔️ Review Column Order: The Optimizer groups by Equality, then Inequality. Ensure the most selective columns are at the front of the key.
  • ✔️ Assess Write/Read Ratio: If a table is 90% writes and 10% reads, a "99% impact" index might actually be a net loss for the system.

🚀 My REAL Strategy

In my 25 years of experience, I’ve seen servers crawl to a halt because a DBA added 50 "Missing Indexes" in a single afternoon. The Optimizer is selfish. It wants the perfect index for *that specific query* without caring about the other 5,000 queries running on that table. My strategy? If a missing index suggestion has less than 80% impact or low user seeks, ignore it. Focus only on the top 5 "High Impact" results and always try to expand an existing index rather than creating a new one.

📊 TAKEAWAY

Indexes are a double-edged sword. Use the DMVs to find the pain points, but use your brain to design the solution. A leaner index strategy always beats a "green text" strategy in high-concurrency environments.

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!

🧠 Master SQL Server Performance Hub

Expand your knowledge with my latest deep-dives and performance guides.

Performance "45 Seconds"

Indexing & Tuning

Execution Plans

SQL 2025 & AI

Don't forget to check my April 2026 Recap for a complete monthly summary.

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, execution plan and the lazy spool (clearly explained)

Image
Hi Guys, Welcome back! In one of the last posts we talked about Table Spool . We had explained what Spool are for by telling the somewhat curious story of the halloween problem . Here we specifically talked about a type of spool called Eager Spool   You can look to the execution plan below where the eager Spool is used to avoid the halloween problem in classic query of the "salary increase".. i suggest Well, if the story of the eager spool intrigued you, today instead we will speak about another type of Spool, the Lazy Spool . The Lazy spool Let's take a small step back. So, what is a Spool operation?  As we have already understood a spool operation is simply a temporary storage of data . Data are read from a source table and stored inside a worktable in the Tempdb database . While an Eager Spool is used to prevent the Halloween problem, the Lazy Spool is instead used to store data that will later be needed again when running a query . So, when a Lazy spool is used?  ...
Read more