You can give SQL Server a query hint, for example. force him to use a specific index - but as far as I know, there is no way to prevent the use of a specific index. Can you find another index that might use your query?
In addition, with SQL Server 2008, you have new additional query hints, called OPTIMIZE FOR, that can help you determine (and explain) the query optimizer why it should optimize.
See the MSDN documentation for tooltips for more information .
This is a typical and fundamental compromise that you must make when adding indexes - yes, it can increase the performance of one query that you are looking at, but at the same time it can lead to a decrease in others. There really is no easy solution - either the gain for another query is more than the pain for that query, and then save the index. Otherwise release it.
source
share