We love the long-term index usage data. We'd love it even more with additional enhancements like below:

1. Availability via Redgate Monitor MCP interface. We have AI processes that would greatly benefit from access to this long-term trove of important data. The ability to pull index usage data for a given object during a defined timeframe would be ideal. Of course, all the ideas below would apply to this too. ;)

2. Separation of indexes by defnition, not just name. Sometimes an index is rebuilt with a different definition that affects how the index works. It would be good to have a fingerprint as a key with the index-name so we don't accidentally mix pre and post-change data together when analyzing.

3. Indication of data completeness issues... When pulling index data for a timeframe it would be helpful to know if the data is complete or otherwise incongruent. Incomplete data happens for a number of reasons. Among them is certainly a data collection problem due to server or client issues; It could also be that a SQL server restarted more than once between daily data-collections, losing the in-between data.

4. Improved Index GUI in Redgate Monitor... Improved date filter letting us specify a start and end date. A completeness indicator to show when there are gaps in data collection. Inclusion of an index fingerprint so we can separate pre and post data when an index definition changes (but the name stays the same); This could be done inside the existing status column. Customizable columns so we can add things like created date.

5. An effectiveness rating for indexes seems like it could be similar to the impact rating given to queries. What's the cost of updating this index vs the benefit from usage? Is the index unused, over-provisioned, or maybe a good idea but not used very often?

The long-term index data is a hugely useful feature, and we'd like more of it. Thank you!