sql server – Index Drop for Partial Overlap?

I’m working with a 50mil row table with the following:

  • Clustered Index keyed on (Col1)
  • Nonclustered Index keyed on (Col1), (Col2) (no includes)

It seems like the right call here would be to drop #2 and rebuild #1 keyed on (Col1), (Col2). Sound right? Would the tuning logic be the same if the NCI still had (Col1) as its first key and then 7 other keys after that (rebuild the CX with 8 keys)?