• ramana3327 (4/18/2014)


    Thanks Steve.

    So depends on the user seeks count, we can get idea about the dropping of the Index.

    Suppose if you have index1 with one key column and index2 with same key column and with 10 include columns, still in that case also you go by using user seek counts

    It's just hard to say. If SQL Server doesn't need any of those columns, but still thinks the first column is useful, it's more likely to get for the smaller index because it's smaller, even though they're the same. As Steve says, you can evaluate this stuff, bit it's not a hard and fast rule. There's no simple formula that points out this index is bad and this one is good. You can look to your code, your execution plans, the usage statistics, and evaluate from there.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning