GilaMonster (1/8/2013)
It's a seek because you have a SARGable predicate (Col1 > 60 ) on a column that is the leading column of the index.Scan is when you have nothing to seek on and SQL has to read the entire index or table. In this case, there is something to seek on.
Thanks for your response Gail 🙂
I think where we are stuck is;
At the leaf level of the NCI(no include), Col2 is sorted and the evaluation of whether or not the value meets the predicate could be/should be optimised?
In the case of the INCLUDE;
for Col1 = 61, Col2 = {random order}
In the case of the 'COVER';
for Col1 = 61, Col2 = {ordered numbers}
Perhaps we lack a fundamental understanding of what's going on.