• I think testing is the way to go on any of this. But, also check the index usage stats to see if they've been used. If an index has been used, be very cautious in replacing it. Other than that, I think your plan is relatively sound. I'd just be curious if you've looked at the code too. Maybe just using the INCLUDE is all that's needed rather than that compound key, which makes the index much bigger and slower across the B-tree side of it.

    "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