InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comWed, 22 May 2013 20:39:50 GMT20http://www.sqlservercentral.com/Forums/Topic1391318-392-1.aspx[quote][b]Shadab Shah (11/30/2012)[/b][hr]So my basic question is, how does the query analyzer decide when to used ClusteredIndexScan and when to used ClusteredIndexSeek.[/quote]It will often consider both alternatives. It estimates the cost of each and chooses the one that appears cheapest (according to the model it uses). There are a number of detailed factors that affect the cost calculation, and overall plan selection, but that's a basic answer to your basic question.Sat, 01 Dec 2012 22:38:54 GMTPaul Whitehttp://www.sqlservercentral.com/Forums/Topic1391318-392-1.aspx[quote][b]ScottPletcher (11/30/2012)[/b][hr][quote][b]Grant Fritchey (11/30/2012)[/b][hr]And the indexes have to be selective enough to be useful for a seek or you'll get scans. Same things apply to non-clustered indexes too.For lots more detail on query tuning and execution plans, take a look at my books (listed below).[/quote]Not for clustered indexes. SQL can do a seek on a clustered index even if you're SELECTing 99% of the rows.[/quote]More correctly, not for any index that covers the query. A covering nonclustered index can and will be used for a seek up to 100% of the rows.Fri, 30 Nov 2012 12:49:36 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1391318-392-1.aspx[quote][b]Grant Fritchey (11/30/2012)[/b][hr]And the indexes have to be selective enough to be useful for a seek or you'll get scans. Same things apply to non-clustered indexes too.For lots more detail on query tuning and execution plans, take a look at my books (listed below).[/quote]Not for clustered indexes. SQL can do a seek on a clustered index even if you're SELECTing 99% of the rows.Fri, 30 Nov 2012 12:28:46 GMTScottPletcherhttp://www.sqlservercentral.com/Forums/Topic1391318-392-1.aspxAnd the indexes have to be selective enough to be useful for a seek or you'll get scans. Same things apply to non-clustered indexes too.For lots more detail on query tuning and execution plans, take a look at my books (listed below).Fri, 30 Nov 2012 09:22:55 GMTGrant Fritcheyhttp://www.sqlservercentral.com/Forums/Topic1391318-392-1.aspxSeek when there's a SARGable predicate (<column> <comparison operator> <expression>) on the index key columns. Scan if there isn't. Very, very simplified, but that's the basics.Fri, 30 Nov 2012 08:12:24 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1391318-392-1.aspxPaul White's blog series will pretty much any question you could ever think of on this.[url]http://www.sqlservercentral.com/articles/SQL+Server+2008/71019/[/url]Fri, 30 Nov 2012 08:04:02 GMTDennis Posthttp://www.sqlservercentral.com/Forums/Topic1391318-392-1.aspxHi All,I am a newbie in SQL Server and like exploring it. Currently i was working with some complex queries and happen to see there Execution Plan. I saw that there were some Clustered index which were 'ClusteredIndexSeek' and Some Clustered Index as 'ClusteredIndexScan'. So my basic question is, how does the query analyzer decide when to used ClusteredIndexScan and when to used ClusteredIndexSeek.Fri, 30 Nov 2012 07:52:29 GMTShadab Shah