Finding Missing indexes

Finding Missing indexes


SQL Server registers every missing index. Here is how you retrieve that information from the missing index DMV’s

The WHERE clause contains a filter that only shows the missing indexes for the current databases and only for indexes that are missing for more then 10 times. You can change that how ever you want.


The result is a list of CREATE statements that you can copy and execute in your database. The names of the indexes are somehow prefabricated, you can adjust that formula.


We especially pay attention to the data in the yellow marked area. For example If the amount of rows is very high and the user seeks is very low and the last user seek was a week ago, we wouldn’t create that index of course. But if the rowcount was for example 200000 and the user seeks above 1000 and last user seek actual with current date then yes.

About us

Over the years, SQLTreeo gained precious know-how which we transformed into customer support, managed database services and database solutions.

In order to express our knowledge and experiences, we tend to work with anything less than the best-trained staff and that is the key to success and the biggest asset of our company. Thus, all our database management services are controlled by high level skilled and Senior database administrators.

We can help you in every aspect of SQL Server.

Danny Riebeek

Danny is a SQL Enthusiast, always disovering new ways to leverage SQL Server functionality

View my other posts

One Comment on “Finding Missing indexes”

  1. Chris Harshman says:

    You may want to add the typical disclaimers for looking at the Missing Index DMVs, such as comparing the suggested indexes to already existing indexes because it will recommend duplicates and column order of the suggested index key is fairly random instead of a useful order.

    Here’s a Microsoft article on the problems:

Leave a Reply