<?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; Removing Key Lookup &#8211; Seek Predicate &#8211; Predicate &#8211; An Interesting Observation Related to Datatypes</title>
	<atom:link href="http://blog.sqlauthority.com/2009/11/09/sql-server-removing-key-lookup-seek-predicate-predicate-an-interesting-observation-related-to-datatypes/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.sqlauthority.com/2009/11/09/sql-server-removing-key-lookup-seek-predicate-predicate-an-interesting-observation-related-to-datatypes/</link>
	<description>Personal Notes of Pinal Dave</description>
	<lastBuildDate>Sat, 25 May 2013 01:31:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Paresh RathodParesh Rathod</title>
		<link>http://blog.sqlauthority.com/2009/11/09/sql-server-removing-key-lookup-seek-predicate-predicate-an-interesting-observation-related-to-datatypes/#comment-433709</link>
		<dc:creator><![CDATA[Paresh RathodParesh Rathod]]></dc:creator>
		<pubDate>Fri, 08 Mar 2013 05:34:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7088#comment-433709</guid>
		<description><![CDATA[Hi Pinal,

Thanks a lot for detail explanation.

I have sql query with where clause.

Where IsActive = 1

IsActive is bit field in table.

It showing me Predicate with Convert_Implicit in query execution plan for above column.

Now I convert where clause like

Where IsActive = CAST(1 AS BIT)

Even it showing me Predicate like IsActive=(1)

Plan also showing Clustered Index Seek in above both cases


Is there any performance problem in above both cases, please elaborate more on this.]]></description>
		<content:encoded><![CDATA[<p>Hi Pinal,</p>
<p>Thanks a lot for detail explanation.</p>
<p>I have sql query with where clause.</p>
<p>Where IsActive = 1</p>
<p>IsActive is bit field in table.</p>
<p>It showing me Predicate with Convert_Implicit in query execution plan for above column.</p>
<p>Now I convert where clause like</p>
<p>Where IsActive = CAST(1 AS BIT)</p>
<p>Even it showing me Predicate like IsActive=(1)</p>
<p>Plan also showing Clustered Index Seek in above both cases</p>
<p>Is there any performance problem in above both cases, please elaborate more on this.</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/11/09/sql-server-removing-key-lookup-seek-predicate-predicate-an-interesting-observation-related-to-datatypes/#comment-393516</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:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7088#comment-393516</guid>
		<description><![CDATA[[...] Removing Key Lookup – Seek Predicate – Predicate – An Interesting Observation Related to Data...This is one of the most important performance tuning lesson on my blog. I suggest this weekend you spend time reading them and let me know what you think about the concepts which I have demonstrated in the four part series. [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Removing Key Lookup – Seek Predicate – Predicate – An Interesting Observation Related to Data&#8230;This is one of the most important performance tuning lesson on my blog. I suggest this weekend you spend time reading them and let me know what you think about the concepts which I have demonstrated in the four part series. [...]</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/11/09/sql-server-removing-key-lookup-seek-predicate-predicate-an-interesting-observation-related-to-datatypes/#comment-371919</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:15 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7088#comment-371919</guid>
		<description><![CDATA[[...] Removing Key Lookup – Seek Predicate – Predicate – An Interesting Observation Related to Datat... Performance Tuning is an interesting concept and my personal favorite one. In many blog posts I have described how to do performance tuning and how to improve the performance of the queries. In this quick quick tip I have explained how one can remove the Key Lookup and improve performance. [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Removing Key Lookup – Seek Predicate – Predicate – An Interesting Observation Related to Datat&#8230; Performance Tuning is an interesting concept and my personal favorite one. In many blog posts I have described how to do performance tuning and how to improve the performance of the queries. In this quick quick tip I have explained how one can remove the Key Lookup and improve performance. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AVK</title>
		<link>http://blog.sqlauthority.com/2009/11/09/sql-server-removing-key-lookup-seek-predicate-predicate-an-interesting-observation-related-to-datatypes/#comment-369874</link>
		<dc:creator><![CDATA[AVK]]></dc:creator>
		<pubDate>Mon, 05 Nov 2012 22:19:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7088#comment-369874</guid>
		<description><![CDATA[Posted on the incorrect thread]]></description>
		<content:encoded><![CDATA[<p>Posted on the incorrect thread</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AVK</title>
		<link>http://blog.sqlauthority.com/2009/11/09/sql-server-removing-key-lookup-seek-predicate-predicate-an-interesting-observation-related-to-datatypes/#comment-369870</link>
		<dc:creator><![CDATA[AVK]]></dc:creator>
		<pubDate>Mon, 05 Nov 2012 22:18:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7088#comment-369870</guid>
		<description><![CDATA[Hi , 

This might be a very simple question but however just wanted to ask as I&#039;m kind off stuck at  a point. I&#039;m trying to create a filtered index on a column, but I&#039;m not able to because I&#039;m getting a syntax error. I checked if this is permission issue, but that&#039;s not the case, because I&#039;m able to create and alter indexes and also use other option in the create index syntax. 

CREATE NONCLUSTERED INDEX &quot;IX_test_NC&quot; ON   
dbo.Table_name (column_name)
WHERE substring(column_name,1,3) = &#039;value&#039; 

The error is : 

Msg 156, Level 15, State 1, Line 4
Incorrect syntax near the keyword &#039;WHERE&#039;.]]></description>
		<content:encoded><![CDATA[<p>Hi , </p>
<p>This might be a very simple question but however just wanted to ask as I&#8217;m kind off stuck at  a point. I&#8217;m trying to create a filtered index on a column, but I&#8217;m not able to because I&#8217;m getting a syntax error. I checked if this is permission issue, but that&#8217;s not the case, because I&#8217;m able to create and alter indexes and also use other option in the create index syntax. </p>
<p>CREATE NONCLUSTERED INDEX &#8220;IX_test_NC&#8221; ON<br />
dbo.Table_name (column_name)<br />
WHERE substring(column_name,1,3) = &#8216;value&#8217; </p>
<p>The error is : </p>
<p>Msg 156, Level 15, State 1, Line 4<br />
Incorrect syntax near the keyword &#8216;WHERE&#8217;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Soma</title>
		<link>http://blog.sqlauthority.com/2009/11/09/sql-server-removing-key-lookup-seek-predicate-predicate-an-interesting-observation-related-to-datatypes/#comment-355258</link>
		<dc:creator><![CDATA[Soma]]></dc:creator>
		<pubDate>Tue, 02 Oct 2012 22:16:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7088#comment-355258</guid>
		<description><![CDATA[Good one.]]></description>
		<content:encoded><![CDATA[<p>Good one.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Danny</title>
		<link>http://blog.sqlauthority.com/2009/11/09/sql-server-removing-key-lookup-seek-predicate-predicate-an-interesting-observation-related-to-datatypes/#comment-354026</link>
		<dc:creator><![CDATA[Danny]]></dc:creator>
		<pubDate>Fri, 28 Sep 2012 20:12:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7088#comment-354026</guid>
		<description><![CDATA[Excellent, thank you very much!!!]]></description>
		<content:encoded><![CDATA[<p>Excellent, thank you very much!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ashok Kumar J</title>
		<link>http://blog.sqlauthority.com/2009/11/09/sql-server-removing-key-lookup-seek-predicate-predicate-an-interesting-observation-related-to-datatypes/#comment-304228</link>
		<dc:creator><![CDATA[Ashok Kumar J]]></dc:creator>
		<pubDate>Fri, 22 Jun 2012 07:11:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7088#comment-304228</guid>
		<description><![CDATA[Alter Way of Leftouter join method?

Can anyone give me the method of alter way of left outer join Because when we create a indexed view we could not able create index on theat view due to statement contains FULL JOIN or LEFT JOIN or RIGHT JOIN. So i searched the web fully it gives suggestion using UNION Instead of left join,I mentioned query below. So could you give me any other method is available to replace LEFT JOIN with that other than UNION? Is it full to reduce optimization cost when we use UNION instead of LEFT JOIN? Quick suggestions are highly appreciated.............buddys.........

----------------------My original table using left join method-----------------

SELECT tablea.*,
CASE
WHEN tableb.tablebcolumn1 IS NULL THEN 0
ELSE 1
END IsHosted
FROM tablea
LEFT JOIN tableb ON tablea.column=tableb.column

-----------Example of alter way of using UNIONALL instead of leftouterjoin ---------

SELECT tablea.,
CASE
WHEN tableb.tablebcolumn1 IS NULL THEN 0
ELSE 1
END IsHosted
FROM tablea where tablea.column IN (select tableb.column from tableb) UNION ALL SELECT tablea.,
CASE
WHEN tableb.tablebcolumn1 IS NULL THEN 0
ELSE 1
END IsHosted
FROM tablea where tablea.column NOT IN (select tableb.column from tableb)

-------------------------------------------------------------------------------------- Note: Due to security reason i did not give original table name. i gave table name of tablea and tableb.........as my originaltable name]]></description>
		<content:encoded><![CDATA[<p>Alter Way of Leftouter join method?</p>
<p>Can anyone give me the method of alter way of left outer join Because when we create a indexed view we could not able create index on theat view due to statement contains FULL JOIN or LEFT JOIN or RIGHT JOIN. So i searched the web fully it gives suggestion using UNION Instead of left join,I mentioned query below. So could you give me any other method is available to replace LEFT JOIN with that other than UNION? Is it full to reduce optimization cost when we use UNION instead of LEFT JOIN? Quick suggestions are highly appreciated&#8230;&#8230;&#8230;&#8230;.buddys&#8230;&#8230;&#8230;</p>
<p>&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;-My original table using left join method&#8212;&#8212;&#8212;&#8212;&#8212;&#8211;</p>
<p>SELECT tablea.*,<br />
CASE<br />
WHEN tableb.tablebcolumn1 IS NULL THEN 0<br />
ELSE 1<br />
END IsHosted<br />
FROM tablea<br />
LEFT JOIN tableb ON tablea.column=tableb.column</p>
<p>&#8212;&#8212;&#8212;&#8211;Example of alter way of using UNIONALL instead of leftouterjoin &#8212;&#8212;&#8212;</p>
<p>SELECT tablea.,<br />
CASE<br />
WHEN tableb.tablebcolumn1 IS NULL THEN 0<br />
ELSE 1<br />
END IsHosted<br />
FROM tablea where tablea.column IN (select tableb.column from tableb) UNION ALL SELECT tablea.,<br />
CASE<br />
WHEN tableb.tablebcolumn1 IS NULL THEN 0<br />
ELSE 1<br />
END IsHosted<br />
FROM tablea where tablea.column NOT IN (select tableb.column from tableb)</p>
<p>&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8211; Note: Due to security reason i did not give original table name. i gave table name of tablea and tableb&#8230;&#8230;&#8230;as my originaltable name</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: irena</title>
		<link>http://blog.sqlauthority.com/2009/11/09/sql-server-removing-key-lookup-seek-predicate-predicate-an-interesting-observation-related-to-datatypes/#comment-288550</link>
		<dc:creator><![CDATA[irena]]></dc:creator>
		<pubDate>Fri, 25 May 2012 13:27:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7088#comment-288550</guid>
		<description><![CDATA[great post helped me solve problem i had with one query
thanks]]></description>
		<content:encoded><![CDATA[<p>great post helped me solve problem i had with one query<br />
thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aditi</title>
		<link>http://blog.sqlauthority.com/2009/11/09/sql-server-removing-key-lookup-seek-predicate-predicate-an-interesting-observation-related-to-datatypes/#comment-287168</link>
		<dc:creator><![CDATA[Aditi]]></dc:creator>
		<pubDate>Tue, 22 May 2012 12:24:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7088#comment-287168</guid>
		<description><![CDATA[Good Article..]]></description>
		<content:encoded><![CDATA[<p>Good Article..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kamesh</title>
		<link>http://blog.sqlauthority.com/2009/11/09/sql-server-removing-key-lookup-seek-predicate-predicate-an-interesting-observation-related-to-datatypes/#comment-258136</link>
		<dc:creator><![CDATA[Kamesh]]></dc:creator>
		<pubDate>Thu, 01 Mar 2012 06:22:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7088#comment-258136</guid>
		<description><![CDATA[Hi Sir,

    I cant get the answer for the following question from my senior colleagues so i am escalting to you.I dont know if it belong to this post or not.but after reading this i came across this problem

	Question is something like my isolation  level is set to read committed.Which is default for SQL SERVER.Now i am doing a explicit transaction(Where When i will execute commit after that only my data will get committed).In this situation.

	I have a table of 100 rows.I am executing one update on table which will affect 10 rows.This update wont get committ.

	First doubt :  Is it after each single row will be updated and then that row related index will be updated?
			or After updating 10 rows Index will be updated for all 10 rows.??

	Second doubt : After committ only my belonging index will be updated or before committ and how??

	Please if you want i can try to explain further my problem.


Thanks 
Kamesh]]></description>
		<content:encoded><![CDATA[<p>Hi Sir,</p>
<p>    I cant get the answer for the following question from my senior colleagues so i am escalting to you.I dont know if it belong to this post or not.but after reading this i came across this problem</p>
<p>	Question is something like my isolation  level is set to read committed.Which is default for SQL SERVER.Now i am doing a explicit transaction(Where When i will execute commit after that only my data will get committed).In this situation.</p>
<p>	I have a table of 100 rows.I am executing one update on table which will affect 10 rows.This update wont get committ.</p>
<p>	First doubt :  Is it after each single row will be updated and then that row related index will be updated?<br />
			or After updating 10 rows Index will be updated for all 10 rows.??</p>
<p>	Second doubt : After committ only my belonging index will be updated or before committ and how??</p>
<p>	Please if you want i can try to explain further my problem.</p>
<p>Thanks<br />
Kamesh</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Supraja</title>
		<link>http://blog.sqlauthority.com/2009/11/09/sql-server-removing-key-lookup-seek-predicate-predicate-an-interesting-observation-related-to-datatypes/#comment-250984</link>
		<dc:creator><![CDATA[Supraja]]></dc:creator>
		<pubDate>Fri, 10 Feb 2012 15:00:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7088#comment-250984</guid>
		<description><![CDATA[Hi, This is really an excellent article.
Thanks Pinal, for sharing your knowledge with us.]]></description>
		<content:encoded><![CDATA[<p>Hi, This is really an excellent article.<br />
Thanks Pinal, for sharing your knowledge with us.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim White</title>
		<link>http://blog.sqlauthority.com/2009/11/09/sql-server-removing-key-lookup-seek-predicate-predicate-an-interesting-observation-related-to-datatypes/#comment-250976</link>
		<dc:creator><![CDATA[Tim White]]></dc:creator>
		<pubDate>Fri, 10 Feb 2012 14:20:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7088#comment-250976</guid>
		<description><![CDATA[I may be wrong here, but the way I understand this is when comparing different Data Types, the difference between a &quot;Seek Predicate&quot; and a &quot;Predicate&quot; is based on the Data Type Precedence.  The Data Type with the lower precedence is the one that is always converted.  So, if the lower precedence Data Type is on the left side (table side), every row gets converted (Full Index Scan).  If the lower precedence is on the right side (expression side), only the expression value gets converetd (Index Seek).

See:  http://msdn.microsoft.com/en-us/library/ms190309.aspx  for precedence order.]]></description>
		<content:encoded><![CDATA[<p>I may be wrong here, but the way I understand this is when comparing different Data Types, the difference between a &#8220;Seek Predicate&#8221; and a &#8220;Predicate&#8221; is based on the Data Type Precedence.  The Data Type with the lower precedence is the one that is always converted.  So, if the lower precedence Data Type is on the left side (table side), every row gets converted (Full Index Scan).  If the lower precedence is on the right side (expression side), only the expression value gets converetd (Index Seek).</p>
<p>See:  <a href="http://msdn.microsoft.com/en-us/library/ms190309.aspx" rel="nofollow">http://msdn.microsoft.com/en-us/library/ms190309.aspx</a>  for precedence order.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hari</title>
		<link>http://blog.sqlauthority.com/2009/11/09/sql-server-removing-key-lookup-seek-predicate-predicate-an-interesting-observation-related-to-datatypes/#comment-187919</link>
		<dc:creator><![CDATA[Hari]]></dc:creator>
		<pubDate>Thu, 03 Nov 2011 20:40:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7088#comment-187919</guid>
		<description><![CDATA[Thank you Pinal. it is very HelpFull Article]]></description>
		<content:encoded><![CDATA[<p>Thank you Pinal. it is very HelpFull Article</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob</title>
		<link>http://blog.sqlauthority.com/2009/11/09/sql-server-removing-key-lookup-seek-predicate-predicate-an-interesting-observation-related-to-datatypes/#comment-149884</link>
		<dc:creator><![CDATA[Bob]]></dc:creator>
		<pubDate>Thu, 21 Jul 2011 21:37:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7088#comment-149884</guid>
		<description><![CDATA[If you turn on IO statistics and the query is doing a convert from varchar to say nvarchar.  One can see the impact in the elasped time, the hit is not in the query plan. It is overhead in converting the data to a comparable data type.
If there are a large number of rows this is a very unwanted overhead and it will take your query longer to complete.]]></description>
		<content:encoded><![CDATA[<p>If you turn on IO statistics and the query is doing a convert from varchar to say nvarchar.  One can see the impact in the elasped time, the hit is not in the query plan. It is overhead in converting the data to a comparable data type.<br />
If there are a large number of rows this is a very unwanted overhead and it will take your query longer to complete.</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/11/09/sql-server-removing-key-lookup-seek-predicate-predicate-an-interesting-observation-related-to-datatypes/#comment-149242</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:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7088#comment-149242</guid>
		<description><![CDATA[[...] (Read more here) [...]]]></description>
		<content:encoded><![CDATA[<p>[...] (Read more here) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sim</title>
		<link>http://blog.sqlauthority.com/2009/11/09/sql-server-removing-key-lookup-seek-predicate-predicate-an-interesting-observation-related-to-datatypes/#comment-128761</link>
		<dc:creator><![CDATA[Sim]]></dc:creator>
		<pubDate>Thu, 14 Apr 2011 03:02:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7088#comment-128761</guid>
		<description><![CDATA[If my query is: SELECT * FROM tablename WHERE field1=value and field1 already is a nonclustered index, after executing, and look at actual execution plan, i saw Index Seek on field1 and Key Lookup on primary key, how i gonna remove this Key Lookup since i cant include all field as covering index?]]></description>
		<content:encoded><![CDATA[<p>If my query is: SELECT * FROM tablename WHERE field1=value and field1 already is a nonclustered index, after executing, and look at actual execution plan, i saw Index Seek on field1 and Key Lookup on primary key, how i gonna remove this Key Lookup since i cant include all field as covering index?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: STANLY PRINCE</title>
		<link>http://blog.sqlauthority.com/2009/11/09/sql-server-removing-key-lookup-seek-predicate-predicate-an-interesting-observation-related-to-datatypes/#comment-127422</link>
		<dc:creator><![CDATA[STANLY PRINCE]]></dc:creator>
		<pubDate>Thu, 07 Apr 2011 18:40:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7088#comment-127422</guid>
		<description><![CDATA[Hi,  This is a wonderful tips.  really helpful.]]></description>
		<content:encoded><![CDATA[<p>Hi,  This is a wonderful tips.  really helpful.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Johnny</title>
		<link>http://blog.sqlauthority.com/2009/11/09/sql-server-removing-key-lookup-seek-predicate-predicate-an-interesting-observation-related-to-datatypes/#comment-105988</link>
		<dc:creator><![CDATA[Johnny]]></dc:creator>
		<pubDate>Wed, 15 Dec 2010 19:30:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7088#comment-105988</guid>
		<description><![CDATA[In your example, you select three columns, so it makes sense to create a NONCLUSTERED INDEX.  If we select 30 columns, does it still make sense to create a NONCLUSTERED INDEX? Thanks.]]></description>
		<content:encoded><![CDATA[<p>In your example, you select three columns, so it makes sense to create a NONCLUSTERED INDEX.  If we select 30 columns, does it still make sense to create a NONCLUSTERED INDEX? Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Amit D. Kulkarni</title>
		<link>http://blog.sqlauthority.com/2009/11/09/sql-server-removing-key-lookup-seek-predicate-predicate-an-interesting-observation-related-to-datatypes/#comment-95722</link>
		<dc:creator><![CDATA[Amit D. Kulkarni]]></dc:creator>
		<pubDate>Mon, 25 Oct 2010 14:18:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7088#comment-95722</guid>
		<description><![CDATA[I found your document very useful.
After spending hours for performance tuning related material on net I found your article the best one. Please share me more info on EXECUTION PLAN and PERFORMANCE TUNING.
Thanks again
AMit :)]]></description>
		<content:encoded><![CDATA[<p>I found your document very useful.<br />
After spending hours for performance tuning related material on net I found your article the best one. Please share me more info on EXECUTION PLAN and PERFORMANCE TUNING.<br />
Thanks again<br />
AMit :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lakshmipathyg</title>
		<link>http://blog.sqlauthority.com/2009/11/09/sql-server-removing-key-lookup-seek-predicate-predicate-an-interesting-observation-related-to-datatypes/#comment-71543</link>
		<dc:creator><![CDATA[Lakshmipathyg]]></dc:creator>
		<pubDate>Wed, 19 May 2010 06:47:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7088#comment-71543</guid>
		<description><![CDATA[Thank you so much for sharing, it was excellent]]></description>
		<content:encoded><![CDATA[<p>Thank you so much for sharing, it was excellent</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Abhilash</title>
		<link>http://blog.sqlauthority.com/2009/11/09/sql-server-removing-key-lookup-seek-predicate-predicate-an-interesting-observation-related-to-datatypes/#comment-58060</link>
		<dc:creator><![CDATA[Abhilash]]></dc:creator>
		<pubDate>Tue, 01 Dec 2009 10:09:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7088#comment-58060</guid>
		<description><![CDATA[Ah! the one I&#039;s looking for.
Thats a nice scribbling.

Thanks.]]></description>
		<content:encoded><![CDATA[<p>Ah! the one I&#8217;s looking for.<br />
Thats a nice scribbling.</p>
<p>Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Schutz</title>
		<link>http://blog.sqlauthority.com/2009/11/09/sql-server-removing-key-lookup-seek-predicate-predicate-an-interesting-observation-related-to-datatypes/#comment-57812</link>
		<dc:creator><![CDATA[Dave Schutz]]></dc:creator>
		<pubDate>Mon, 23 Nov 2009 00:57:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7088#comment-57812</guid>
		<description><![CDATA[Very informative article on Key lookups. I like the way it was broken down into separate articles, easier to follow.]]></description>
		<content:encoded><![CDATA[<p>Very informative article on Key lookups. I like the way it was broken down into separate articles, easier to follow.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shilesh Rastogi</title>
		<link>http://blog.sqlauthority.com/2009/11/09/sql-server-removing-key-lookup-seek-predicate-predicate-an-interesting-observation-related-to-datatypes/#comment-57629</link>
		<dc:creator><![CDATA[Shilesh Rastogi]]></dc:creator>
		<pubDate>Mon, 16 Nov 2009 06:27:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7088#comment-57629</guid>
		<description><![CDATA[Hi Pinal, 

This is a great article and very informative.]]></description>
		<content:encoded><![CDATA[<p>Hi Pinal, </p>
<p>This is a great article and very informative.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tobin</title>
		<link>http://blog.sqlauthority.com/2009/11/09/sql-server-removing-key-lookup-seek-predicate-predicate-an-interesting-observation-related-to-datatypes/#comment-57539</link>
		<dc:creator><![CDATA[Tobin]]></dc:creator>
		<pubDate>Thu, 12 Nov 2009 06:11:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7088#comment-57539</guid>
		<description><![CDATA[Good Article!!!!!]]></description>
		<content:encoded><![CDATA[<p>Good Article!!!!!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
