• So looking at the queries, it really is nothing more than the lack of a covering index. This is normal behavior. The query is returning enough results that a table scan in the absence of a covering index is more efficient.

    If you create a covering index for the second of the two queries, both queries should be able to use (better yet, modify the first index to add the extra column(s)).

    Jason...AKA CirqueDeSQLeil
    _______________________________________________
    I have given a name to my pain...MCM SQL Server, MVP
    SQL RNNR
    Posting Performance Based Questions - Gail Shaw[/url]
    Learn Extended Events