Seems I managed to make it through all of April without an update to the index analysis stored procedure. It wasn’t for lack of using it with clients, but a lack of time to get the changes out the door.
A few months back, I added the option to look at just duplicate index or overlapping index results. Have you taken the opportunity to use those features? If so, I’d like to hear from you to find out if the output is sufficient to make judgments on dropping the or modifying your indexes. Please reach out or leave a comment so I can make those sections better.
Index Analysis Updated
There are a couple tweaks that I forgot about documenting in this update. Though, the main updates to the script in this release are the following:
- Fixed overlapping index logic that was made wonky because of duplicate index changes (see That’s Actually A Duplicate Index for more about duplicate indexes)
- Adjusted missing foreign key logic to remove duplicate responses
Index Analysis Download
Get the current versions of the Index Analysis script from GitHub.
Comments and More Information
Let me know if you run into any issues with these scripts, my e-mail address is in the header of all of the procedures. If you are looking for a few hundred pages of indexing information, you can check out Expert Performance Indexing for SQL Server 2012. Along with that, for indexing resources from my blog, check out the index resource page.
Lastly, want to see this script do anything special with indexes? Leave a comment and I’ll see what I can do.
8 thoughts on “Index Analysis May Update”
Do you have missing indexes finder query too?
what changes do we need to analyze all tables instead of a single table?
Hello, I Think there are a error in your code.
Your version (Left), My Correction (Right).
Do you agree ?
Thank’s a lot for this script 🙂
Looks like the index action returns the default for “Missing Foreign Key” and “Missing Index” when it should be returning “Create” or “Blend.” The attached image shows the corrections that I think are needed.
Thanks, Luke. I’ll take a look. I’ve got an update to this coming out soon with some more outputs, as well.
Comments are closed.