'SQL Server doesn't use missing indexes after it creation

I ran into a very strange situation. I have a query and the optimizer advises to create an missing index for one of the tables. For example

create index on table1 (id) include (dt);

After the index is created, the optimizer doesn't use it, but advise to create the same index! Never experienced this kind of behavior before. Can anyone suggest how to force SQL server to use the existing indexes?

sqlsql-serverindexing


Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution Source

Related Questions