GilaMonster (1/9/2013)
dwilliscp (1/9/2013)
I was trying to find a better approach than what I am currently doing... that is starting with the query, pulling the top 10 and looking at what tables they are using (to see if there are any indexes on them, and if they are similuar). Then I look at the execution and see if they are spending a lot of time doing table scans (well it is a percent, but you get the idea). I guess the one change is to work my way down to do all those with 1000 ranking or higher.Don't start with missing index stats. That's cart before horse. Start with queries that have poor performance. You're indexing to improve query performance, no indexing to remove entries from a list of index suggestions.
Ok must be missing something... the only other way I know.. of keeping things tuned.. is the trace that I have running with every reboot. It traps anything with SET @DurationFilter > 180000000. (3 min run time) If this is what you are talking about.. then why would you ever run the query looking for missing index?