Index Analysis (including Missing Indexes)

I would have to say having more information would be good not bad.  I get that poor database design is often the issue but there's more than one way to skin a cat.

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.

That's the kind of the point.  I can run queries for all the wait stats too, but why not show some possible indexes while you are using DPA? 

Why?  Because essentially it is not needed.   You can determine if it is an indexing issue by looking at the execution plan, and running something like sp_BlitzIndex to see what indexes exist for a table *AND* what's in the missing index DMVs.  Not to mention, the larger the query (i.e. more tables / views), I think it's unrealistic to try and map missing indexes to your query programmatically.

I *always* go back to the developer when they use SELECT * to confirm the queries cannot be "tuned down" first.