January 29, 2009 at 12:29 pm
ScottPletcher (1/29/2009)
I never said it was doing a seek, I said it was using the index. It looked to me like SQL was scanning the non-clus index to get the key values to hash, rather than scanning the full table.
Where do you see that? In the execution plan, the operator is Table Scan (ie scan of the heap), not Index Scan for all of the occurrences of sysValidationList. The nonclustered index isn't mentioned at all.
The only index scans in the plan are against the Person table (using the pk_Person index) and the AssignmentDetails table (using the IX_AssignmentDetails index). Both are clustered index scans, so again a read of the entire table.
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
January 29, 2009 at 1:13 pm
I was reading the textual plan, not the graphical one, which at a quick look I thought was using IX_sysValidationList index.
SQL DBA,SQL Server MVP(07, 08, 09) "It's a dog-eat-dog world, and I'm wearing Milk-Bone underwear." "Norm", on "Cheers". Also from "Cheers", from "Carla": "You need to know 3 things about Tortelli men: Tortelli men draw women like flies; Tortelli men treat women like flies; Tortelli men's brains are in their flies".
Viewing 2 posts - 31 through 31 (of 31 total)
You must be logged in to reply to this topic. Login to reply