Home Forums SQL Server 2012 SQL Server 2012 - T-SQL Non-clustered Covering Indexes - Many w/few included columns vs Single w/many included columns RE: Non-clustered Covering Indexes - Many w/few included columns vs Single w/many included columns

  • Yup, consolidate, that should be one index.

    The only counter case for keeping it separate would be where queries that use those indexes absolutely must run as fast as possible and not a microsecond more, in that limited case you would probably want multiple indexes for the fastest access possible (larger indexes = more data).

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass