Microsoft SQL Server has great tooling for identifying missing indexes. Each missing index is identified and its potential benefits are projected.
So everything is good as you get to hopefully increase performance without working too hard at it.
But, those running on Microsoft SQL Server – v2008/R2; in our case Microsoft SQL Server 2008 R2 (SP1) [10.50.2500] should be on the look-out.
BTW, using old SQL (@@version) our version is listed below:
Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64) Jun 17 2011 00:54:03 Copyright (c) Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)
So you take SQL Server advise and you create some of those indexes, but the system continues to ask you to create it.
Paul S. Randle blogging has SQLSkills has a good handle on this:
Missing Index DMVs bugs that could cost your sanity
I like his title: … cost your sanity.
That alone suffices for me — already too much mental illness out there…
Write things down, share publicly, and add key words … hopefully, you validate someone’s else thoughts and concerns.
This is to Paul & Kimberly…
So what is Paul’s advice? Apply latest service pack.
BTW, I like the fact that Microsoft is now identifying that the machine is an Hypervisior when one issues the @@version command.
I have to go look for what property to query on to determine visualization flag when issuing ServerProperty command.
- Missing Index dmvs bugs that could cost your sanity
- Missing Index feature an index which is already present