InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comFri, 24 May 2013 00:12:46 GMT20http://www.sqlservercentral.com/Forums/Topic777915-360-1.aspxOops. I forgot to add a link to the blog.[url=http://scarydba.wordpress.com/2009/03/02/more-refinements-on-the-missing-indexes-query/]Here it is.[/url]Thu, 27 Aug 2009 11:18:40 GMTGrant Fritcheyhttp://www.sqlservercentral.com/Forums/Topic777915-360-1.aspx[quote][b]Ryan D. (8/27/2009)[/b][hr]Thank for the reply, the issue I'm having is that the report is showing about 200 missing/recommend indexes. Based upon the different column values, which one should be looked at in the order of importance.[/quote]You more than likely will not need to implement all of the "missing" indexes shown in the report. Sometimes the report will show multiple indexes for the same thing.As Grant has mentioned, there are scripts here on SSC for determining which indexes might be of more use than others (based on cost/benefit).Just Browse the Index Management section of the scripts area here at SSC - or do a search for index scripts. There are several scripts that could be of use.Thu, 27 Aug 2009 09:57:41 GMTSQLRNNRhttp://www.sqlservercentral.com/Forums/Topic777915-360-1.aspx[quote][b]Ryan D. (8/26/2009)[/b][hr]Hi,I have a question regarding the missing indexes section of the performance dashboard. What is the best way to approach the recommended indexes?[/quote]Slowly, maintain eye contact, and carry a really big stick...Oh, you mean how do decide which one's to implement.I wouldn't recommend that you use that data by itself. I'd combine it with a collection of long running queries and most frequently called queries. You'll need to collect that with a server side trace. Then, unfortunately, there's no easy way to marry the missing index data to specific queries... Unless you do something like I blogged about here. There are some other people that have also posted scripts that do the same thing (several of them better than mine) so you can do a search to track them down.Once you decide that a query and a missing index match up and you're ready to use the index, test it. The missing index information is based on estimates within the optimizer, and it can be wrong.Thu, 27 Aug 2009 07:15:12 GMTGrant Fritcheyhttp://www.sqlservercentral.com/Forums/Topic777915-360-1.aspxThank for the reply, the issue I'm having is that the report is showing about 200 missing/recommend indexes. Based upon the different column values, which one should be looked at in the order of importance.Thu, 27 Aug 2009 07:03:47 GMTRyan D.http://www.sqlservercentral.com/Forums/Topic777915-360-1.aspxI like to affix a cost / benefit value to the missing index (number of updates vs. number of lookups as part of it). From there, try to associate the most beneficial recommended missing index with poorly performing queries.Test your indexing in dev and move the indexes up through the ranks to prod during maintenance windows.Wed, 26 Aug 2009 17:52:46 GMTSQLRNNRhttp://www.sqlservercentral.com/Forums/Topic777915-360-1.aspxHi,I have a question regarding the missing indexes section of the performance dashboard. What is the best way to approach the recommended indexes?Wed, 26 Aug 2009 15:47:50 GMTRyan D.