<?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; Query Optimization &#8211; Remove Bookmark Lookup &#8211; Remove RID Lookup &#8211; Remove Key Lookup</title>
	<atom:link href="http://blog.sqlauthority.com/2009/10/07/sql-server-query-optimization-remove-bookmark-lookup-remove-rid-lookup-remove-key-lookup/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.sqlauthority.com/2009/10/07/sql-server-query-optimization-remove-bookmark-lookup-remove-rid-lookup-remove-key-lookup/</link>
	<description>Personal Notes of Pinal Dave</description>
	<lastBuildDate>Thu, 23 May 2013 14:22:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Steven</title>
		<link>http://blog.sqlauthority.com/2009/10/07/sql-server-query-optimization-remove-bookmark-lookup-remove-rid-lookup-remove-key-lookup/#comment-458689</link>
		<dc:creator><![CDATA[Steven]]></dc:creator>
		<pubDate>Thu, 18 Apr 2013 14:30:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=6960#comment-458689</guid>
		<description><![CDATA[Hello Pinal,

Very clear and informative.  Understanding tuning is tricky but this post made it seem simple.

My question is, when creating the composite index, why do you specify city first, rather than ID, which is more unique.

Thanks,
Steven]]></description>
		<content:encoded><![CDATA[<p>Hello Pinal,</p>
<p>Very clear and informative.  Understanding tuning is tricky but this post made it seem simple.</p>
<p>My question is, when creating the composite index, why do you specify city first, rather than ID, which is more unique.</p>
<p>Thanks,<br />
Steven</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sik</title>
		<link>http://blog.sqlauthority.com/2009/10/07/sql-server-query-optimization-remove-bookmark-lookup-remove-rid-lookup-remove-key-lookup/#comment-411961</link>
		<dc:creator><![CDATA[Sik]]></dc:creator>
		<pubDate>Wed, 23 Jan 2013 19:28:54 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=6960#comment-411961</guid>
		<description><![CDATA[Hi, 
great article, i find it very helpful...
I have a question... what happens when the output list of a key lookup is NULL? what is it looking for?]]></description>
		<content:encoded><![CDATA[<p>Hi,<br />
great article, i find it very helpful&#8230;<br />
I have a question&#8230; what happens when the output list of a key lookup is NULL? what is it looking for?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SQL SERVER &#8211; Weekly Series &#8211; Memory Lane &#8211; #007 &#171; SQL Server Journey with SQL Authority</title>
		<link>http://blog.sqlauthority.com/2009/10/07/sql-server-query-optimization-remove-bookmark-lookup-remove-rid-lookup-remove-key-lookup/#comment-393517</link>
		<dc:creator><![CDATA[SQL SERVER &#8211; Weekly Series &#8211; Memory Lane &#8211; #007 &#171; SQL Server Journey with SQL Authority]]></dc:creator>
		<pubDate>Sat, 15 Dec 2012 01:31:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=6960#comment-393517</guid>
		<description><![CDATA[[...] Part 1 &#124; Part 2 &#124; Part 3 &#124; Part 4 [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Part 1 | Part 2 | Part 3 | Part 4 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SQL SERVER &#8211; Beginning New Weekly Series &#8211; Memory Lane &#8211; #002 &#171; SQL Server Journey with SQL Authority</title>
		<link>http://blog.sqlauthority.com/2009/10/07/sql-server-query-optimization-remove-bookmark-lookup-remove-rid-lookup-remove-key-lookup/#comment-371920</link>
		<dc:creator><![CDATA[SQL SERVER &#8211; Beginning New Weekly Series &#8211; Memory Lane &#8211; #002 &#171; SQL Server Journey with SQL Authority]]></dc:creator>
		<pubDate>Sat, 10 Nov 2012 01:31:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=6960#comment-371920</guid>
		<description><![CDATA[[...] are very relevant articles on this subject: Article 1 &#124; Article 2 &#124; Article [...]]]></description>
		<content:encoded><![CDATA[<p>[...] are very relevant articles on this subject: Article 1 | Article 2 | Article [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Girijesh Pandey</title>
		<link>http://blog.sqlauthority.com/2009/10/07/sql-server-query-optimization-remove-bookmark-lookup-remove-rid-lookup-remove-key-lookup/#comment-355092</link>
		<dc:creator><![CDATA[Girijesh Pandey]]></dc:creator>
		<pubDate>Tue, 02 Oct 2012 08:00:58 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=6960#comment-355092</guid>
		<description><![CDATA[Hi Pinal,

Nice explanation, too easy to understand.

i have one question over here, let me write your code what you have used.

SELECT ID, FirstName
FROM OneIndex
WHERE City = &#039;Las Vegas&#039;

CREATE NONCLUSTERED INDEX [IX_OneIndex_Include] ON [dbo].[OneIndex]
(
City
) INCLUDE (FirstName,ID) ON [PRIMARY]
GO

As i can see in above code, you are selecting ID then FirstName columns in Select list, but while including these columns for Non Clustered Index you have not followed the same sequence/order (Included Firstname then ID)

Is this really fruitful to improve query performance?

As per my understanding, we should follow the same sequence as we are selecting the fields, same sequence should be followed while including in Index,   It would be easy for SQL Server to get the data in fast way.

Regards,
Girijesh]]></description>
		<content:encoded><![CDATA[<p>Hi Pinal,</p>
<p>Nice explanation, too easy to understand.</p>
<p>i have one question over here, let me write your code what you have used.</p>
<p>SELECT ID, FirstName<br />
FROM OneIndex<br />
WHERE City = &#8216;Las Vegas&#8217;</p>
<p>CREATE NONCLUSTERED INDEX [IX_OneIndex_Include] ON [dbo].[OneIndex]<br />
(<br />
City<br />
) INCLUDE (FirstName,ID) ON [PRIMARY]<br />
GO</p>
<p>As i can see in above code, you are selecting ID then FirstName columns in Select list, but while including these columns for Non Clustered Index you have not followed the same sequence/order (Included Firstname then ID)</p>
<p>Is this really fruitful to improve query performance?</p>
<p>As per my understanding, we should follow the same sequence as we are selecting the fields, same sequence should be followed while including in Index,   It would be easy for SQL Server to get the data in fast way.</p>
<p>Regards,<br />
Girijesh</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hemant K</title>
		<link>http://blog.sqlauthority.com/2009/10/07/sql-server-query-optimization-remove-bookmark-lookup-remove-rid-lookup-remove-key-lookup/#comment-233985</link>
		<dc:creator><![CDATA[Hemant K]]></dc:creator>
		<pubDate>Mon, 09 Jan 2012 06:01:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=6960#comment-233985</guid>
		<description><![CDATA[Hi,
If you are saying, if table has clustered index, it is called bookmark lookup (or key lookup); if the table does not have clustered index, but a non-clustered index, it is called RID lookup then you again wrote that as we have an index on the WHERE clause, the SQL Server query execution engine uses the non-clustered index to retrieve data from the table. However, the columns used in the SELECT clause (id, firstname) are still not part of the index that means (neither cluster index nor non-cluster index has applied on it)and to display those columns, the engine will have to go to the base table again and retrieve those columns. so how we can say this particular behavior is known as bookmark lookup or key lookup]]></description>
		<content:encoded><![CDATA[<p>Hi,<br />
If you are saying, if table has clustered index, it is called bookmark lookup (or key lookup); if the table does not have clustered index, but a non-clustered index, it is called RID lookup then you again wrote that as we have an index on the WHERE clause, the SQL Server query execution engine uses the non-clustered index to retrieve data from the table. However, the columns used in the SELECT clause (id, firstname) are still not part of the index that means (neither cluster index nor non-cluster index has applied on it)and to display those columns, the engine will have to go to the base table again and retrieve those columns. so how we can say this particular behavior is known as bookmark lookup or key lookup</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SQL SERVER &#8211; An Important Part of Most SELECT statement &#8211; WHERE clause &#8211; Quiz &#8211; Puzzle &#8211; 4 of 31 &#171; SQL Server Journey with SQL Authority</title>
		<link>http://blog.sqlauthority.com/2009/10/07/sql-server-query-optimization-remove-bookmark-lookup-remove-rid-lookup-remove-key-lookup/#comment-231551</link>
		<dc:creator><![CDATA[SQL SERVER &#8211; An Important Part of Most SELECT statement &#8211; WHERE clause &#8211; Quiz &#8211; Puzzle &#8211; 4 of 31 &#171; SQL Server Journey with SQL Authority]]></dc:creator>
		<pubDate>Thu, 05 Jan 2012 01:32:15 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=6960#comment-231551</guid>
		<description><![CDATA[[...] Questions and Answers ISBN: 1466405643 Page#38-40 Does Order of Column in WHERE clause Matter? Query Optimization – Remove Bookmark Lookup – Remove RID Lookup – Remove Key Lookup Logical Query Processing Phases – Order of Statement [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Questions and Answers ISBN: 1466405643 Page#38-40 Does Order of Column in WHERE clause Matter? Query Optimization – Remove Bookmark Lookup – Remove RID Lookup – Remove Key Lookup Logical Query Processing Phases – Order of Statement [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: madhivanan</title>
		<link>http://blog.sqlauthority.com/2009/10/07/sql-server-query-optimization-remove-bookmark-lookup-remove-rid-lookup-remove-key-lookup/#comment-182944</link>
		<dc:creator><![CDATA[madhivanan]]></dc:creator>
		<pubDate>Mon, 24 Oct 2011 15:52:37 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=6960#comment-182944</guid>
		<description><![CDATA[Search for &quot;delete duplicate values&quot; in this site. You will get related articles]]></description>
		<content:encoded><![CDATA[<p>Search for &#8220;delete duplicate values&#8221; in this site. You will get related articles</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: stanly</title>
		<link>http://blog.sqlauthority.com/2009/10/07/sql-server-query-optimization-remove-bookmark-lookup-remove-rid-lookup-remove-key-lookup/#comment-181517</link>
		<dc:creator><![CDATA[stanly]]></dc:creator>
		<pubDate>Fri, 21 Oct 2011 08:54:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=6960#comment-181517</guid>
		<description><![CDATA[how can i remove duplicate records in a table and after deleting duplicate records i need one distinct record]]></description>
		<content:encoded><![CDATA[<p>how can i remove duplicate records in a table and after deleting duplicate records i need one distinct record</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SQL SERVER – Interview Questions and Answers – Frequently Asked Questions – Day 19 of 31 Journey to SQLAuthority</title>
		<link>http://blog.sqlauthority.com/2009/10/07/sql-server-query-optimization-remove-bookmark-lookup-remove-rid-lookup-remove-key-lookup/#comment-149237</link>
		<dc:creator><![CDATA[SQL SERVER – Interview Questions and Answers – Frequently Asked Questions – Day 19 of 31 Journey to SQLAuthority]]></dc:creator>
		<pubDate>Tue, 19 Jul 2011 01:30:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=6960#comment-149237</guid>
		<description><![CDATA[[...] In the above scenario, if table has clustered index, it is called bookmark lookup (or key lookup); if the table does not have clustered index, but a non-clustered index, it is called RID lookup. (Read more here) [...]]]></description>
		<content:encoded><![CDATA[<p>[...] In the above scenario, if table has clustered index, it is called bookmark lookup (or key lookup); if the table does not have clustered index, but a non-clustered index, it is called RID lookup. (Read more here) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nidhi</title>
		<link>http://blog.sqlauthority.com/2009/10/07/sql-server-query-optimization-remove-bookmark-lookup-remove-rid-lookup-remove-key-lookup/#comment-125372</link>
		<dc:creator><![CDATA[Nidhi]]></dc:creator>
		<pubDate>Mon, 28 Mar 2011 15:06:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=6960#comment-125372</guid>
		<description><![CDATA[HI Pinal,

Thanks for this post.Its very easy to understand.Good post.]]></description>
		<content:encoded><![CDATA[<p>HI Pinal,</p>
<p>Thanks for this post.Its very easy to understand.Good post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Duckstein</title>
		<link>http://blog.sqlauthority.com/2009/10/07/sql-server-query-optimization-remove-bookmark-lookup-remove-rid-lookup-remove-key-lookup/#comment-97256</link>
		<dc:creator><![CDATA[Nick Duckstein]]></dc:creator>
		<pubDate>Mon, 01 Nov 2010 23:53:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=6960#comment-97256</guid>
		<description><![CDATA[Dave,

I&#039;m confused why the best recommendation isn&#039;t to create a clustered index. In our situation we have a 5 Billion row table without a clustered index. The RID lookups are killing us. The need for a lot of extra non-clustered indexes is also killing performance because this is on a replication server.

Finally the writes to a clustered index are dramatically less than to a non-clustered index with a HEAP.

See: http://msdn.microsoft.com/en-us/library/cc917672.aspx#EFAA

How can anyone justify a large table without a clustered index?

Nick]]></description>
		<content:encoded><![CDATA[<p>Dave,</p>
<p>I&#8217;m confused why the best recommendation isn&#8217;t to create a clustered index. In our situation we have a 5 Billion row table without a clustered index. The RID lookups are killing us. The need for a lot of extra non-clustered indexes is also killing performance because this is on a replication server.</p>
<p>Finally the writes to a clustered index are dramatically less than to a non-clustered index with a HEAP.</p>
<p>See: <a href="http://msdn.microsoft.com/en-us/library/cc917672.aspx#EFAA" rel="nofollow">http://msdn.microsoft.com/en-us/library/cc917672.aspx#EFAA</a></p>
<p>How can anyone justify a large table without a clustered index?</p>
<p>Nick</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sridhar Nalluri</title>
		<link>http://blog.sqlauthority.com/2009/10/07/sql-server-query-optimization-remove-bookmark-lookup-remove-rid-lookup-remove-key-lookup/#comment-76329</link>
		<dc:creator><![CDATA[Sridhar Nalluri]]></dc:creator>
		<pubDate>Tue, 15 Jun 2010 08:43:21 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=6960#comment-76329</guid>
		<description><![CDATA[Hi Pinal,

Nice post, very impressive and understandable...Thank You.]]></description>
		<content:encoded><![CDATA[<p>Hi Pinal,</p>
<p>Nice post, very impressive and understandable&#8230;Thank You.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SQL SERVER – Four Posts on Removing the Bookmark Lookup – Key Lookup Journey to SQL Authority with Pinal Dave</title>
		<link>http://blog.sqlauthority.com/2009/10/07/sql-server-query-optimization-remove-bookmark-lookup-remove-rid-lookup-remove-key-lookup/#comment-70650</link>
		<dc:creator><![CDATA[SQL SERVER – Four Posts on Removing the Bookmark Lookup – Key Lookup Journey to SQL Authority with Pinal Dave]]></dc:creator>
		<pubDate>Thu, 13 May 2010 01:31:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=6960#comment-70650</guid>
		<description><![CDATA[[...] SQL SERVER – Query Optimization – Remove Bookmark Lookup – Remove RID Lookup – Remove Key Lo... [...]]]></description>
		<content:encoded><![CDATA[<p>[...] SQL SERVER – Query Optimization – Remove Bookmark Lookup – Remove RID Lookup – Remove Key Lo&#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ronald Lee</title>
		<link>http://blog.sqlauthority.com/2009/10/07/sql-server-query-optimization-remove-bookmark-lookup-remove-rid-lookup-remove-key-lookup/#comment-59534</link>
		<dc:creator><![CDATA[Ronald Lee]]></dc:creator>
		<pubDate>Sun, 10 Jan 2010 07:10:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=6960#comment-59534</guid>
		<description><![CDATA[Excellent Post!!!  Thank you for the information.  This helps me improve my SP from 5 seconds to 0.xx second.  Thanks alot!]]></description>
		<content:encoded><![CDATA[<p>Excellent Post!!!  Thank you for the information.  This helps me improve my SP from 5 seconds to 0.xx second.  Thanks alot!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Chapman</title>
		<link>http://blog.sqlauthority.com/2009/10/07/sql-server-query-optimization-remove-bookmark-lookup-remove-rid-lookup-remove-key-lookup/#comment-57843</link>
		<dc:creator><![CDATA[Mike Chapman]]></dc:creator>
		<pubDate>Mon, 23 Nov 2009 19:49:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=6960#comment-57843</guid>
		<description><![CDATA[Awesome.  Managed to knock down a query from 5-6 minutes down to 5 seconds or so.]]></description>
		<content:encoded><![CDATA[<p>Awesome.  Managed to knock down a query from 5-6 minutes down to 5 seconds or so.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SQL SERVER – Remove Bookmark Key Lookup – 4 Different Ideas Journey to SQL Authority with Pinal Dave</title>
		<link>http://blog.sqlauthority.com/2009/10/07/sql-server-query-optimization-remove-bookmark-lookup-remove-rid-lookup-remove-key-lookup/#comment-57790</link>
		<dc:creator><![CDATA[SQL SERVER – Remove Bookmark Key Lookup – 4 Different Ideas Journey to SQL Authority with Pinal Dave]]></dc:creator>
		<pubDate>Sun, 22 Nov 2009 01:32:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=6960#comment-57790</guid>
		<description><![CDATA[[...] SQL SERVER – Query Optimization – Remove Bookmark Lookup – Remove RID Lookup – Remove Key Lo... [...]]]></description>
		<content:encoded><![CDATA[<p>[...] SQL SERVER – Query Optimization – Remove Bookmark Lookup – Remove RID Lookup – Remove Key Lo&#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DBTEAM</title>
		<link>http://blog.sqlauthority.com/2009/10/07/sql-server-query-optimization-remove-bookmark-lookup-remove-rid-lookup-remove-key-lookup/#comment-57670</link>
		<dc:creator><![CDATA[DBTEAM]]></dc:creator>
		<pubDate>Tue, 17 Nov 2009 13:51:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=6960#comment-57670</guid>
		<description><![CDATA[Hi pinal,

   We have a requirement to Merge six 12millions data tables into single Table.All the tables are having duplicate Emails.So We put the Primary key for email column using EnterPrise Manager and We r trying to merge by writing the following insert query, But it&#039;s taking more than 20hrs...:-(

Insert into Total( Email,FirstName,LastName,Address,City,State,Zipcode,Gender,DOB ,
Phone,WebAddress1,Webaddress2,IPAddress,DateTime,Interest  )
Select Email,FirstName,LastName,Address,City,State,Zipcode,Gender,DOB ,
Phone,WebAddress1,Webaddress2,IPAddress,DateTime,Interest 
From  [Set4]
Where 
(not exists(select email from Total
       where Total.email=[Set4].email))

How can we do this most efficiently??? Please Help Us......

Thanks in advance...]]></description>
		<content:encoded><![CDATA[<p>Hi pinal,</p>
<p>   We have a requirement to Merge six 12millions data tables into single Table.All the tables are having duplicate Emails.So We put the Primary key for email column using EnterPrise Manager and We r trying to merge by writing the following insert query, But it&#8217;s taking more than 20hrs&#8230;:-(</p>
<p>Insert into Total( Email,FirstName,LastName,Address,City,State,Zipcode,Gender,DOB ,<br />
Phone,WebAddress1,Webaddress2,IPAddress,DateTime,Interest  )<br />
Select Email,FirstName,LastName,Address,City,State,Zipcode,Gender,DOB ,<br />
Phone,WebAddress1,Webaddress2,IPAddress,DateTime,Interest<br />
From  [Set4]<br />
Where<br />
(not exists(select email from Total<br />
       where Total.email=[Set4].email))</p>
<p>How can we do this most efficiently??? Please Help Us&#8230;&#8230;</p>
<p>Thanks in advance&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SQL SERVER – Removing Key Lookup – Seek Predicate – Predicate – An Interesting Observation Related to Datatypes Journey to SQL Authority with Pinal Dave</title>
		<link>http://blog.sqlauthority.com/2009/10/07/sql-server-query-optimization-remove-bookmark-lookup-remove-rid-lookup-remove-key-lookup/#comment-57441</link>
		<dc:creator><![CDATA[SQL SERVER – Removing Key Lookup – Seek Predicate – Predicate – An Interesting Observation Related to Datatypes Journey to SQL Authority with Pinal Dave]]></dc:creator>
		<pubDate>Mon, 09 Nov 2009 01:31:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=6960#comment-57441</guid>
		<description><![CDATA[[...] SQL SERVER – Query Optimization – Remove Bookmark Lookup – Remove RID Lookup – Remove Key Lo... [...]]]></description>
		<content:encoded><![CDATA[<p>[...] SQL SERVER – Query Optimization – Remove Bookmark Lookup – Remove RID Lookup – Remove Key Lo&#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Barbara37</title>
		<link>http://blog.sqlauthority.com/2009/10/07/sql-server-query-optimization-remove-bookmark-lookup-remove-rid-lookup-remove-key-lookup/#comment-56930</link>
		<dc:creator><![CDATA[Barbara37]]></dc:creator>
		<pubDate>Fri, 23 Oct 2009 10:54:58 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=6960#comment-56930</guid>
		<description><![CDATA[And these new notes were not just plain bank notes. ,]]></description>
		<content:encoded><![CDATA[<p>And these new notes were not just plain bank notes. ,</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pinaldave</title>
		<link>http://blog.sqlauthority.com/2009/10/07/sql-server-query-optimization-remove-bookmark-lookup-remove-rid-lookup-remove-key-lookup/#comment-56658</link>
		<dc:creator><![CDATA[pinaldave]]></dc:creator>
		<pubDate>Tue, 13 Oct 2009 11:58:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=6960#comment-56658</guid>
		<description><![CDATA[Hi jfbergeron,

Please read my follow up post here : 
SQL SERVER – Query Optimization – Remove Bookmark Lookup – Remove RID Lookup – Remove Key Lookup – Part 3
http://blog.sqlauthority.com/2009/10/12/sql-server-query-optimization-remove-bookmark-lookup-remove-rid-lookup-remove-key-lookup-part-3

Kind Regards,
Pinal]]></description>
		<content:encoded><![CDATA[<p>Hi jfbergeron,</p>
<p>Please read my follow up post here :<br />
SQL SERVER – Query Optimization – Remove Bookmark Lookup – Remove RID Lookup – Remove Key Lookup – Part 3<br />
<a href="http://blog.sqlauthority.com/2009/10/12/sql-server-query-optimization-remove-bookmark-lookup-remove-rid-lookup-remove-key-lookup-part-3" rel="nofollow">http://blog.sqlauthority.com/2009/10/12/sql-server-query-optimization-remove-bookmark-lookup-remove-rid-lookup-remove-key-lookup-part-3</a></p>
<p>Kind Regards,<br />
Pinal</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jfbergeron</title>
		<link>http://blog.sqlauthority.com/2009/10/07/sql-server-query-optimization-remove-bookmark-lookup-remove-rid-lookup-remove-key-lookup/#comment-56653</link>
		<dc:creator><![CDATA[jfbergeron]]></dc:creator>
		<pubDate>Tue, 13 Oct 2009 11:11:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=6960#comment-56653</guid>
		<description><![CDATA[Hi Pinal,

I&#039;m curious to know why you have included the ID column in the covering index, as well as in the nc index with the includes. I thought all columns in the Clustered index were already included in the non clustered index.

Is there a reason why you did that?

Thanks,]]></description>
		<content:encoded><![CDATA[<p>Hi Pinal,</p>
<p>I&#8217;m curious to know why you have included the ID column in the covering index, as well as in the nc index with the includes. I thought all columns in the Clustered index were already included in the non clustered index.</p>
<p>Is there a reason why you did that?</p>
<p>Thanks,</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SQL SERVER – Query Optimization – Remove Bookmark Lookup – Remove RID Lookup – Remove Key Lookup – Part 3 Journey to SQL Authority with Pinal Dave</title>
		<link>http://blog.sqlauthority.com/2009/10/07/sql-server-query-optimization-remove-bookmark-lookup-remove-rid-lookup-remove-key-lookup/#comment-56599</link>
		<dc:creator><![CDATA[SQL SERVER – Query Optimization – Remove Bookmark Lookup – Remove RID Lookup – Remove Key Lookup – Part 3 Journey to SQL Authority with Pinal Dave]]></dc:creator>
		<pubDate>Mon, 12 Oct 2009 01:31:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=6960#comment-56599</guid>
		<description><![CDATA[[...] SQL SERVER – Query Optimization – Remove Bookmark Lookup – Remove RID Lookup – Remove Key Lo... [...]]]></description>
		<content:encoded><![CDATA[<p>[...] SQL SERVER – Query Optimization – Remove Bookmark Lookup – Remove RID Lookup – Remove Key Lo&#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SQL SERVER – Query Optimization – Remove Bookmark Lookup – Remove RID Lookup – Remove Key Lookup – Part 2 Journey to SQL Authority with Pinal Dave</title>
		<link>http://blog.sqlauthority.com/2009/10/07/sql-server-query-optimization-remove-bookmark-lookup-remove-rid-lookup-remove-key-lookup/#comment-56514</link>
		<dc:creator><![CDATA[SQL SERVER – Query Optimization – Remove Bookmark Lookup – Remove RID Lookup – Remove Key Lookup – Part 2 Journey to SQL Authority with Pinal Dave]]></dc:creator>
		<pubDate>Thu, 08 Oct 2009 01:31:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=6960#comment-56514</guid>
		<description><![CDATA[[...] 8, 2009 by pinaldave    This article is follow up of my previous article SQL SERVER &#8211; Query Optimization &#8211; Remove Bookmark Lookup &#8211; Remove RID Lookup &amp;#821.... Please do read my previous article before continuing [...]]]></description>
		<content:encoded><![CDATA[<p>[...] 8, 2009 by pinaldave    This article is follow up of my previous article SQL SERVER &#8211; Query Optimization &#8211; Remove Bookmark Lookup &#8211; Remove RID Lookup &amp;#821&#8230;. Please do read my previous article before continuing [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pinaldave</title>
		<link>http://blog.sqlauthority.com/2009/10/07/sql-server-query-optimization-remove-bookmark-lookup-remove-rid-lookup-remove-key-lookup/#comment-56512</link>
		<dc:creator><![CDATA[pinaldave]]></dc:creator>
		<pubDate>Thu, 08 Oct 2009 00:58:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=6960#comment-56512</guid>
		<description><![CDATA[Hi,

If we do not need those columns in query for SURE they need to be removed. I agree with you there.

I will send you other details soon.

Kind Regards,
Pinal]]></description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>If we do not need those columns in query for SURE they need to be removed. I agree with you there.</p>
<p>I will send you other details soon.</p>
<p>Kind Regards,<br />
Pinal</p>
]]></content:encoded>
	</item>
</channel>
</rss>
