Implemented

Index Analysis (including Missing Indexes)

Since databasses report missing index data, it would be nice to see this in DPA so we can associate the largest wait time sql with missing index data.

Provide analysis about current indexes on a table

Show unused or underused indexes.

10/12/16 - changed header and description to reflect the feature better

This feature has been implemented in DPA 12.0 and is now available for download in the customer portal

See these posts for more information about DPA 12.0.

FormerMember
FormerMember
Parents
  • I don't understand the reluctance for some to receive index recommendations.  As stated previously, I would rather have the information and determine whether or not to add the index.  While it is possible to add too many indexes to a table, indexing is the key to performance (no pun intended).  As a DBA working on performance issues, your options are to; 1 - rewrite the query, which is sometimes your best option if possible, 2 - change the structure of the database, i.e. de-normalize, etc., or 3 - add an index.

  • I know it's a little old of a topic but after seeing it's available in Beta I thought I'd chime in.  There was so much "aggression" towards the fact that people wanted to see Index analysis or index recommendations in the application.  I cannot see a reason why it would be a bad thing to have multiple places to validate whether or not an index is needed.  Sometimes the execution plan won't give you the obvious "MISSING INDEX HINT"  you have to look at the COST for each operator and validate whether an index is needed - Sp_blitzIndex is not always the end all be all for "missing indexes" sure it's a nice to have but I don't trust everything that it provides either.  Leave it up to the DBA monitoring the system to add the index in lower life cycles and see if it's worth the add or not  Why prohibit us from seeing it?  Are you seriously that angry about having an index recommended? If that's the case and you're such a DBA Purist or DBA Savant - don't use DPA at all, use the dmv's and write your own nifty powershell scripts to populate a repository of your own and build a front end to display want you want.  (this isn't geared towards you at all, I agree w/ you) I just cannot see  how this is a negative.  Solarwinds would be doing the consumer a disservice by not having this as part of the suite of options.

Comment
  • I know it's a little old of a topic but after seeing it's available in Beta I thought I'd chime in.  There was so much "aggression" towards the fact that people wanted to see Index analysis or index recommendations in the application.  I cannot see a reason why it would be a bad thing to have multiple places to validate whether or not an index is needed.  Sometimes the execution plan won't give you the obvious "MISSING INDEX HINT"  you have to look at the COST for each operator and validate whether an index is needed - Sp_blitzIndex is not always the end all be all for "missing indexes" sure it's a nice to have but I don't trust everything that it provides either.  Leave it up to the DBA monitoring the system to add the index in lower life cycles and see if it's worth the add or not  Why prohibit us from seeing it?  Are you seriously that angry about having an index recommended? If that's the case and you're such a DBA Purist or DBA Savant - don't use DPA at all, use the dmv's and write your own nifty powershell scripts to populate a repository of your own and build a front end to display want you want.  (this isn't geared towards you at all, I agree w/ you) I just cannot see  how this is a negative.  Solarwinds would be doing the consumer a disservice by not having this as part of the suite of options.

Children
No Data