<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: SQL SERVER &#8211; Index Seek Vs. Index Scan (Table Scan)</title>
	<atom:link href="http://blog.sqlauthority.com/2007/03/30/sql-server-index-seek-vs-index-scan-table-scan/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.sqlauthority.com/2007/03/30/sql-server-index-seek-vs-index-scan-table-scan/</link>
	<description>Personal Notes of Pinal Dave</description>
	<lastBuildDate>Thu, 09 Feb 2012 10:40:10 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Anusha</title>
		<link>http://blog.sqlauthority.com/2007/03/30/sql-server-index-seek-vs-index-scan-table-scan/#comment-213788</link>
		<dc:creator><![CDATA[Anusha]]></dc:creator>
		<pubDate>Fri, 09 Dec 2011 03:00:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2007/03/30/index-seek-vs-index-scan-table-scan/#comment-213788</guid>
		<description><![CDATA[I have a table with M pages .IIf i want to retreive its data without index .What will be the cost of processing - full table one row retireval,full  table one column retrieval,subset of table one row retrieval....
If I use B+ index can i improve the query processing...Please answer urgently I am in dire need of this answer]]></description>
		<content:encoded><![CDATA[<p>I have a table with M pages .IIf i want to retreive its data without index .What will be the cost of processing &#8211; full table one row retireval,full  table one column retrieval,subset of table one row retrieval&#8230;.<br />
If I use B+ index can i improve the query processing&#8230;Please answer urgently I am in dire need of this answer</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Amel Musić</title>
		<link>http://blog.sqlauthority.com/2007/03/30/sql-server-index-seek-vs-index-scan-table-scan/#comment-186421</link>
		<dc:creator><![CDATA[Amel Musić]]></dc:creator>
		<pubDate>Tue, 01 Nov 2011 14:03:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2007/03/30/index-seek-vs-index-scan-table-scan/#comment-186421</guid>
		<description><![CDATA[Did you try &quot;Select * From Table with(nolock)&quot; ?]]></description>
		<content:encoded><![CDATA[<p>Did you try &#8220;Select * From Table with(nolock)&#8221; ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: madhivanan</title>
		<link>http://blog.sqlauthority.com/2007/03/30/sql-server-index-seek-vs-index-scan-table-scan/#comment-186411</link>
		<dc:creator><![CDATA[madhivanan]]></dc:creator>
		<pubDate>Tue, 01 Nov 2011 13:35:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2007/03/30/index-seek-vs-index-scan-table-scan/#comment-186411</guid>
		<description><![CDATA[What happens when you run it for second time? Also check if the table is blocked by other processes]]></description>
		<content:encoded><![CDATA[<p>What happens when you run it for second time? Also check if the table is blocked by other processes</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rahul</title>
		<link>http://blog.sqlauthority.com/2007/03/30/sql-server-index-seek-vs-index-scan-table-scan/#comment-186370</link>
		<dc:creator><![CDATA[rahul]]></dc:creator>
		<pubDate>Tue, 01 Nov 2011 11:15:54 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2007/03/30/index-seek-vs-index-scan-table-scan/#comment-186370</guid>
		<description><![CDATA[Hi Pinal,

I have a table which has 5000 rows of data in it. When i try to use a simple query &quot;Select * From Table&quot; its taking 20 seconds of time. I did not use any where conditions in my query. Its a just &quot;Select * From Table&quot;. I have different data type columns in my table including bit datatypes. I dont know how to improve the performance of my query. Please, help me in this.]]></description>
		<content:encoded><![CDATA[<p>Hi Pinal,</p>
<p>I have a table which has 5000 rows of data in it. When i try to use a simple query &#8220;Select * From Table&#8221; its taking 20 seconds of time. I did not use any where conditions in my query. Its a just &#8220;Select * From Table&#8221;. I have different data type columns in my table including bit datatypes. I dont know how to improve the performance of my query. Please, help me in this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Thompson</title>
		<link>http://blog.sqlauthority.com/2007/03/30/sql-server-index-seek-vs-index-scan-table-scan/#comment-179860</link>
		<dc:creator><![CDATA[Dan Thompson]]></dc:creator>
		<pubDate>Mon, 17 Oct 2011 09:44:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2007/03/30/index-seek-vs-index-scan-table-scan/#comment-179860</guid>
		<description><![CDATA[Hi Pinal,

I would disagree....see my post: http://www.techtree.co.uk/2011/10/table-scan-vs-index-scan/]]></description>
		<content:encoded><![CDATA[<p>Hi Pinal,</p>
<p>I would disagree&#8230;.see my post: <a href="http://www.techtree.co.uk/2011/10/table-scan-vs-index-scan/" rel="nofollow">http://www.techtree.co.uk/2011/10/table-scan-vs-index-scan/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Thompson</title>
		<link>http://blog.sqlauthority.com/2007/03/30/sql-server-index-seek-vs-index-scan-table-scan/#comment-177459</link>
		<dc:creator><![CDATA[Dan Thompson]]></dc:creator>
		<pubDate>Tue, 11 Oct 2011 08:56:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2007/03/30/index-seek-vs-index-scan-table-scan/#comment-177459</guid>
		<description><![CDATA[A table scan will occur when no index is available on that table. The table then becomes a heap. so if you do a SELECT * FROM without_index you will get a table scan. If you were to put a clustered index on the table you would get a clustered index scan when performing the same query.]]></description>
		<content:encoded><![CDATA[<p>A table scan will occur when no index is available on that table. The table then becomes a heap. so if you do a SELECT * FROM without_index you will get a table scan. If you were to put a clustered index on the table you would get a clustered index scan when performing the same query.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: vgj</title>
		<link>http://blog.sqlauthority.com/2007/03/30/sql-server-index-seek-vs-index-scan-table-scan/#comment-160520</link>
		<dc:creator><![CDATA[vgj]]></dc:creator>
		<pubDate>Mon, 22 Aug 2011 07:49:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2007/03/30/index-seek-vs-index-scan-table-scan/#comment-160520</guid>
		<description><![CDATA[good]]></description>
		<content:encoded><![CDATA[<p>good</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: vinoth</title>
		<link>http://blog.sqlauthority.com/2007/03/30/sql-server-index-seek-vs-index-scan-table-scan/#comment-142087</link>
		<dc:creator><![CDATA[vinoth]]></dc:creator>
		<pubDate>Sun, 19 Jun 2011 10:46:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2007/03/30/index-seek-vs-index-scan-table-scan/#comment-142087</guid>
		<description><![CDATA[Hi Pinal,
Thanks for all you articles they are very useful.
If Table scan and index scan are the same then why we need to have two terms?
I am having non clustered index on the table as the selectivity of the query returns more rows optimizer choose for Table scan,eventhough I have index on the table why is that behaviour, my execution plan must show index scan right instead of table scan?]]></description>
		<content:encoded><![CDATA[<p>Hi Pinal,<br />
Thanks for all you articles they are very useful.<br />
If Table scan and index scan are the same then why we need to have two terms?<br />
I am having non clustered index on the table as the selectivity of the query returns more rows optimizer choose for Table scan,eventhough I have index on the table why is that behaviour, my execution plan must show index scan right instead of table scan?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeynav</title>
		<link>http://blog.sqlauthority.com/2007/03/30/sql-server-index-seek-vs-index-scan-table-scan/#comment-141051</link>
		<dc:creator><![CDATA[Jeynav]]></dc:creator>
		<pubDate>Wed, 15 Jun 2011 10:03:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2007/03/30/index-seek-vs-index-scan-table-scan/#comment-141051</guid>
		<description><![CDATA[Use charindex or patindex]]></description>
		<content:encoded><![CDATA[<p>Use charindex or patindex</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: aakash</title>
		<link>http://blog.sqlauthority.com/2007/03/30/sql-server-index-seek-vs-index-scan-table-scan/#comment-115122</link>
		<dc:creator><![CDATA[aakash]]></dc:creator>
		<pubDate>Sat, 29 Jan 2011 11:39:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2007/03/30/index-seek-vs-index-scan-table-scan/#comment-115122</guid>
		<description><![CDATA[i have a table with 45000 rows with a column of amount.
i want to create index on it but with conditions.like i want to create an index for amount&gt;98000 rows , so that when i search for amount &gt;98000 , then it do not searches the whole 45,000 rows but only searches the index with amount&gt;98000.
how do i do this?]]></description>
		<content:encoded><![CDATA[<p>i have a table with 45000 rows with a column of amount.<br />
i want to create index on it but with conditions.like i want to create an index for amount&gt;98000 rows , so that when i search for amount &gt;98000 , then it do not searches the whole 45,000 rows but only searches the index with amount&gt;98000.<br />
how do i do this?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: madhivanan</title>
		<link>http://blog.sqlauthority.com/2007/03/30/sql-server-index-seek-vs-index-scan-table-scan/#comment-95848</link>
		<dc:creator><![CDATA[madhivanan]]></dc:creator>
		<pubDate>Tue, 26 Oct 2010 07:38:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2007/03/30/index-seek-vs-index-scan-table-scan/#comment-95848</guid>
		<description><![CDATA[You need to have a calender table which joins with your original table and calculate the absents

select datename(weekday,c.date),count(*) from calender_table as c left join your_table as t
on c.datecol=t.datecol where t.datecol is null]]></description>
		<content:encoded><![CDATA[<p>You need to have a calender table which joins with your original table and calculate the absents</p>
<p>select datename(weekday,c.date),count(*) from calender_table as c left join your_table as t<br />
on c.datecol=t.datecol where t.datecol is null</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: prafull</title>
		<link>http://blog.sqlauthority.com/2007/03/30/sql-server-index-seek-vs-index-scan-table-scan/#comment-95802</link>
		<dc:creator><![CDATA[prafull]]></dc:creator>
		<pubDate>Tue, 26 Oct 2010 02:07:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2007/03/30/index-seek-vs-index-scan-table-scan/#comment-95802</guid>
		<description><![CDATA[i want to print number of days the student remain absent in aschool daywise(like sun mon tu......) in single row from a student table 


[email removed]]]></description>
		<content:encoded><![CDATA[<p>i want to print number of days the student remain absent in aschool daywise(like sun mon tu&#8230;&#8230;) in single row from a student table </p>
<p>[email removed]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike H</title>
		<link>http://blog.sqlauthority.com/2007/03/30/sql-server-index-seek-vs-index-scan-table-scan/#comment-93037</link>
		<dc:creator><![CDATA[Mike H]]></dc:creator>
		<pubDate>Thu, 14 Oct 2010 13:08:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2007/03/30/index-seek-vs-index-scan-table-scan/#comment-93037</guid>
		<description><![CDATA[Vimal, 
Assuming you mean 1st (first) then just use

select top 1 * from table_name]]></description>
		<content:encoded><![CDATA[<p>Vimal,<br />
Assuming you mean 1st (first) then just use</p>
<p>select top 1 * from table_name</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: vimal</title>
		<link>http://blog.sqlauthority.com/2007/03/30/sql-server-index-seek-vs-index-scan-table-scan/#comment-92565</link>
		<dc:creator><![CDATA[vimal]]></dc:creator>
		<pubDate>Wed, 13 Oct 2010 15:38:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2007/03/30/index-seek-vs-index-scan-table-scan/#comment-92565</guid>
		<description><![CDATA[dear sir,

  i am trying to get the i&#039;th row record from the table in sql server 2000,  
for example i give the query 
select * from table_name where row_position=1

if it is possible to get 1&#039;th record from the table?]]></description>
		<content:encoded><![CDATA[<p>dear sir,</p>
<p>  i am trying to get the i&#8217;th row record from the table in sql server 2000,<br />
for example i give the query<br />
select * from table_name where row_position=1</p>
<p>if it is possible to get 1&#8242;th record from the table?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Samit Shah</title>
		<link>http://blog.sqlauthority.com/2007/03/30/sql-server-index-seek-vs-index-scan-table-scan/#comment-91866</link>
		<dc:creator><![CDATA[Samit Shah]]></dc:creator>
		<pubDate>Sat, 09 Oct 2010 00:22:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2007/03/30/index-seek-vs-index-scan-table-scan/#comment-91866</guid>
		<description><![CDATA[Normally I go through your articles and I find it very useful. Could you please suggest when to use clustered index and when to use non-clustered index. What columns should be used for non-clustered index and what columns should be used for clustered index.]]></description>
		<content:encoded><![CDATA[<p>Normally I go through your articles and I find it very useful. Could you please suggest when to use clustered index and when to use non-clustered index. What columns should be used for non-clustered index and what columns should be used for clustered index.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Biswa</title>
		<link>http://blog.sqlauthority.com/2007/03/30/sql-server-index-seek-vs-index-scan-table-scan/#comment-85776</link>
		<dc:creator><![CDATA[Biswa]]></dc:creator>
		<pubDate>Tue, 31 Aug 2010 10:45:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2007/03/30/index-seek-vs-index-scan-table-scan/#comment-85776</guid>
		<description><![CDATA[Hi Pinal,
I have a base view on top of which there are several views.
One of the views which is based on the base view gives timeout errors.

In the execution plan it shows one index seek takes Cost 80%

There are appropriate indexes on the tables.
Can you suggest any more optimization.]]></description>
		<content:encoded><![CDATA[<p>Hi Pinal,<br />
I have a base view on top of which there are several views.<br />
One of the views which is based on the base view gives timeout errors.</p>
<p>In the execution plan it shows one index seek takes Cost 80%</p>
<p>There are appropriate indexes on the tables.<br />
Can you suggest any more optimization.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rick</title>
		<link>http://blog.sqlauthority.com/2007/03/30/sql-server-index-seek-vs-index-scan-table-scan/#comment-79106</link>
		<dc:creator><![CDATA[Rick]]></dc:creator>
		<pubDate>Wed, 07 Jul 2010 17:00:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2007/03/30/index-seek-vs-index-scan-table-scan/#comment-79106</guid>
		<description><![CDATA[Why would sql suddenly change from an index seek configuration to an index scan configuration? We went from screaming fast to no go in one afternoon. What would trigger the change? Since there were no changes made to the database other than additional data, what would automatically trigger this change in sql?]]></description>
		<content:encoded><![CDATA[<p>Why would sql suddenly change from an index seek configuration to an index scan configuration? We went from screaming fast to no go in one afternoon. What would trigger the change? Since there were no changes made to the database other than additional data, what would automatically trigger this change in sql?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marko Parkkola</title>
		<link>http://blog.sqlauthority.com/2007/03/30/sql-server-index-seek-vs-index-scan-table-scan/#comment-68080</link>
		<dc:creator><![CDATA[Marko Parkkola]]></dc:creator>
		<pubDate>Fri, 30 Apr 2010 15:27:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2007/03/30/index-seek-vs-index-scan-table-scan/#comment-68080</guid>
		<description><![CDATA[Yes, you can. But if the columns aren&#039;t selective enough you risk that your composite index isn&#039;t used at all. Also the order of columns inside the index is significant. You have to test and test and test again to see if the index is used or not. 

I would suggest you create the index and check execution plan to see if it&#039;s used. Then wait couple of days so that database can collect enough statistics and check it again. Finally sys.dm_db_index_physical_stats function tells a lot what&#039;s going on with your indexes.

For example I created four composite index in a single table on one of your databases. All of them were used initially but eventually two of them was rendered useless so I dropped them and DB is running like charm.]]></description>
		<content:encoded><![CDATA[<p>Yes, you can. But if the columns aren&#8217;t selective enough you risk that your composite index isn&#8217;t used at all. Also the order of columns inside the index is significant. You have to test and test and test again to see if the index is used or not. </p>
<p>I would suggest you create the index and check execution plan to see if it&#8217;s used. Then wait couple of days so that database can collect enough statistics and check it again. Finally sys.dm_db_index_physical_stats function tells a lot what&#8217;s going on with your indexes.</p>
<p>For example I created four composite index in a single table on one of your databases. All of them were used initially but eventually two of them was rendered useless so I dropped them and DB is running like charm.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: KK</title>
		<link>http://blog.sqlauthority.com/2007/03/30/sql-server-index-seek-vs-index-scan-table-scan/#comment-67974</link>
		<dc:creator><![CDATA[KK]]></dc:creator>
		<pubDate>Fri, 30 Apr 2010 07:06:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2007/03/30/index-seek-vs-index-scan-table-scan/#comment-67974</guid>
		<description><![CDATA[Hi Kumar,

I think you can create a composite Index on the three columns instead of creating indexes on each and every column to reduce space and to optimize the query performance. Correct me any body if i am wrong.]]></description>
		<content:encoded><![CDATA[<p>Hi Kumar,</p>
<p>I think you can create a composite Index on the three columns instead of creating indexes on each and every column to reduce space and to optimize the query performance. Correct me any body if i am wrong.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marko Parkkola</title>
		<link>http://blog.sqlauthority.com/2007/03/30/sql-server-index-seek-vs-index-scan-table-scan/#comment-67065</link>
		<dc:creator><![CDATA[Marko Parkkola]]></dc:creator>
		<pubDate>Tue, 27 Apr 2010 05:36:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2007/03/30/index-seek-vs-index-scan-table-scan/#comment-67065</guid>
		<description><![CDATA[Hi,

Have you tried Sql Server Database Tuning Advisor? It gives you nice list of indexes it thinks would be good. You can even tell it to suggest indexed views.

It&#039;s hard to say which columns you should index just by your where-statement. You could try to index all of those three columns, index per column. After that check Execution Plan to see if indexes are being used or not.]]></description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>Have you tried Sql Server Database Tuning Advisor? It gives you nice list of indexes it thinks would be good. You can even tell it to suggest indexed views.</p>
<p>It&#8217;s hard to say which columns you should index just by your where-statement. You could try to index all of those three columns, index per column. After that check Execution Plan to see if indexes are being used or not.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kumar</title>
		<link>http://blog.sqlauthority.com/2007/03/30/sql-server-index-seek-vs-index-scan-table-scan/#comment-66902</link>
		<dc:creator><![CDATA[kumar]]></dc:creator>
		<pubDate>Mon, 26 Apr 2010 14:16:58 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2007/03/30/index-seek-vs-index-scan-table-scan/#comment-66902</guid>
		<description><![CDATA[hi Pinal ,

i have 10 ten queries on three tables with 10 where conditions on one table.in that 10 ten queries 3 queries uses
where condition below

where city= and state=? and country=?

how indexes i need to create on these table(one or more).

this table getting truncate abd loaded everyday.

Please advise.]]></description>
		<content:encoded><![CDATA[<p>hi Pinal ,</p>
<p>i have 10 ten queries on three tables with 10 where conditions on one table.in that 10 ten queries 3 queries uses<br />
where condition below</p>
<p>where city= and state=? and country=?</p>
<p>how indexes i need to create on these table(one or more).</p>
<p>this table getting truncate abd loaded everyday.</p>
<p>Please advise.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sharad</title>
		<link>http://blog.sqlauthority.com/2007/03/30/sql-server-index-seek-vs-index-scan-table-scan/#comment-66622</link>
		<dc:creator><![CDATA[sharad]]></dc:creator>
		<pubDate>Sat, 24 Apr 2010 10:53:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2007/03/30/index-seek-vs-index-scan-table-scan/#comment-66622</guid>
		<description><![CDATA[how tune any query]]></description>
		<content:encoded><![CDATA[<p>how tune any query</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marko Parkkola</title>
		<link>http://blog.sqlauthority.com/2007/03/30/sql-server-index-seek-vs-index-scan-table-scan/#comment-60329</link>
		<dc:creator><![CDATA[Marko Parkkola]]></dc:creator>
		<pubDate>Thu, 28 Jan 2010 13:35:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2007/03/30/index-seek-vs-index-scan-table-scan/#comment-60329</guid>
		<description><![CDATA[Easy. Insert the select statement to Sql Server Management Studio and press CTRL+L. Check Execution Plan if it&#039;s using Index Seek or Index Scan.

Check this MSDN article also:

http://technet.microsoft.com/en-us/library/ms189562.aspx

These articles and their subarticles might help also:

http://technet.microsoft.com/en-us/library/ms191227.aspx
http://technet.microsoft.com/en-us/library/ms345417.aspx]]></description>
		<content:encoded><![CDATA[<p>Easy. Insert the select statement to Sql Server Management Studio and press CTRL+L. Check Execution Plan if it&#8217;s using Index Seek or Index Scan.</p>
<p>Check this MSDN article also:</p>
<p><a href="http://technet.microsoft.com/en-us/library/ms189562.aspx" rel="nofollow">http://technet.microsoft.com/en-us/library/ms189562.aspx</a></p>
<p>These articles and their subarticles might help also:</p>
<p><a href="http://technet.microsoft.com/en-us/library/ms191227.aspx" rel="nofollow">http://technet.microsoft.com/en-us/library/ms191227.aspx</a><br />
<a href="http://technet.microsoft.com/en-us/library/ms345417.aspx" rel="nofollow">http://technet.microsoft.com/en-us/library/ms345417.aspx</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pjr</title>
		<link>http://blog.sqlauthority.com/2007/03/30/sql-server-index-seek-vs-index-scan-table-scan/#comment-60304</link>
		<dc:creator><![CDATA[pjr]]></dc:creator>
		<pubDate>Thu, 28 Jan 2010 04:16:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2007/03/30/index-seek-vs-index-scan-table-scan/#comment-60304</guid>
		<description><![CDATA[Hi,

I have a select statement. How do I know if it is using the index which i created on one of the columns (and this column is included in the select list)]]></description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>I have a select statement. How do I know if it is using the index which i created on one of the columns (and this column is included in the select list)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim</title>
		<link>http://blog.sqlauthority.com/2007/03/30/sql-server-index-seek-vs-index-scan-table-scan/#comment-57390</link>
		<dc:creator><![CDATA[Tim]]></dc:creator>
		<pubDate>Fri, 06 Nov 2009 16:22:51 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/2007/03/30/index-seek-vs-index-scan-table-scan/#comment-57390</guid>
		<description><![CDATA[This is a wonderful topic and I&#039;m glad I found it as it&#039;s the exact answer to a quest that I had about a table today. It helped reduce my query time from 14 seconds to less than 1! 

Great work!
Tim]]></description>
		<content:encoded><![CDATA[<p>This is a wonderful topic and I&#8217;m glad I found it as it&#8217;s the exact answer to a quest that I had about a table today. It helped reduce my query time from 14 seconds to less than 1! </p>
<p>Great work!<br />
Tim</p>
]]></content:encoded>
	</item>
</channel>
</rss>

