Why does SQL Server 2005 Dynamic Management View report a missing index when it is not?

sql-server-2005

Solution

Random thought: What if one of the columns is better declared "DESC"?

This is useful for ORDER BY clauses and I've seen logical IO reduce by half.

Problem

I'm using SQL Server 2005 and the the Dynamic Management View `sys.dm_db_missing_index_details`. It continues to tell me that Table1 really needs an index on ColumnX and ColumnY, but that index already exists! I've even dropped and re-created it a couple times to no avail. More specifics: The view lists Column1 under `equality_columns`. Column2 is listed under `inequality_columns`, so the index I have created is: ``` create index IndexA on Table1 (Column1 asc, Column2 asc) ``` Isn't this exactly the index `sys.dm_db_missing_index_details` is telling me I need?

Original source