Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Teroman
Posting Yak Master
115 Posts |
 Posted - 2001-09-05 : 12:23:00
|
| Hi,ive been optimising, or at least trying, some queries, and putting on useful indexes.One query insists on doing an index scan of the table PK, an auto ID column not in the query, in a search, not an index i put on which is clustered, and contains 2 of the columns i am searching the table onlooking at the query plan it prefers an index scan to a clustered index seek, and its way is faster( i hinted it to use my index so i could see what was happening, it does do a seek).whats going on? it has to scan the index instead of going straight to the correct rows, and it has to then do a bookmark look up so it knows where the rows are.why not use the index i lovingly crafted :(yours confused-lycol |
|
|
|
|
|
Optimiser Madness (??)