<?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 – Adding Column is Expensive by Joining Table Outside View – Limitation of the Views Part 2</title>
	<atom:link href="http://blog.sqlauthority.com/2010/08/26/sql-server-adding-column-is-expensive-limitation-of-the-views-part-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.sqlauthority.com/2010/08/26/sql-server-adding-column-is-expensive-limitation-of-the-views-part-2/</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: SQL SERVER &#8211; Weekly Series &#8211; Memory Lane &#8211; #008 &#171; SQL Server Journey with SQL Authority</title>
		<link>http://blog.sqlauthority.com/2010/08/26/sql-server-adding-column-is-expensive-limitation-of-the-views-part-2/#comment-397394</link>
		<dc:creator><![CDATA[SQL SERVER &#8211; Weekly Series &#8211; Memory Lane &#8211; #008 &#171; SQL Server Journey with SQL Authority]]></dc:creator>
		<pubDate>Sat, 22 Dec 2012 01:32:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=9853#comment-397394</guid>
		<description><![CDATA[[...] Adding Column is Expensive by Joining Table Outside View – Limitation of the View 2 [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Adding Column is Expensive by Joining Table Outside View – Limitation of the View 2 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Smith</title>
		<link>http://blog.sqlauthority.com/2010/08/26/sql-server-adding-column-is-expensive-limitation-of-the-views-part-2/#comment-385805</link>
		<dc:creator><![CDATA[David Smith]]></dc:creator>
		<pubDate>Sun, 02 Dec 2012 20:54:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=9853#comment-385805</guid>
		<description><![CDATA[Yeah! right thanks... better focus the content, we will publish a new article about the code of conduct and tsql etiquette &amp; ethics.

Regards,
David Smith]]></description>
		<content:encoded><![CDATA[<p>Yeah! right thanks&#8230; better focus the content, we will publish a new article about the code of conduct and tsql etiquette &amp; ethics.</p>
<p>Regards,<br />
David Smith</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SQL SERVER – Interview Questions and Answers – Frequently Asked Questions – Data Warehouseing Concepts – Day 20 of 31 Journey to SQLAuthority</title>
		<link>http://blog.sqlauthority.com/2010/08/26/sql-server-adding-column-is-expensive-limitation-of-the-views-part-2/#comment-149461</link>
		<dc:creator><![CDATA[SQL SERVER – Interview Questions and Answers – Frequently Asked Questions – Data Warehouseing Concepts – Day 20 of 31 Journey to SQLAuthority]]></dc:creator>
		<pubDate>Wed, 20 Jul 2011 01:31:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=9853#comment-149461</guid>
		<description><![CDATA[[...] (Read more here) [...]]]></description>
		<content:encoded><![CDATA[<p>[...] (Read more here) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mick</title>
		<link>http://blog.sqlauthority.com/2010/08/26/sql-server-adding-column-is-expensive-limitation-of-the-views-part-2/#comment-148898</link>
		<dc:creator><![CDATA[Mick]]></dc:creator>
		<pubDate>Sun, 17 Jul 2011 10:03:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=9853#comment-148898</guid>
		<description><![CDATA[Thank you, that saved me some time. How much of your time have you spent blogging SQL Server? You must be an online legend at it!

Thanks again, Mick.]]></description>
		<content:encoded><![CDATA[<p>Thank you, that saved me some time. How much of your time have you spent blogging SQL Server? You must be an online legend at it!</p>
<p>Thanks again, Mick.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andreas</title>
		<link>http://blog.sqlauthority.com/2010/08/26/sql-server-adding-column-is-expensive-limitation-of-the-views-part-2/#comment-144651</link>
		<dc:creator><![CDATA[Andreas]]></dc:creator>
		<pubDate>Wed, 29 Jun 2011 12:26:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=9853#comment-144651</guid>
		<description><![CDATA[Two questions:

1) Why are you using SELECT * ... ? As an SQL Authority you should know that not explicitly specifying what columns you need will lead to brittle and potentially underperformant queries.

2) Assuming that you explicitly select the columns you need eg. SELECT [SalesOrderID],[SalesOrderDetailID], ... (see question 1) what is the performance impact of adding an additional column to the view?

Best regards,
Andreas]]></description>
		<content:encoded><![CDATA[<p>Two questions:</p>
<p>1) Why are you using SELECT * &#8230; ? As an SQL Authority you should know that not explicitly specifying what columns you need will lead to brittle and potentially underperformant queries.</p>
<p>2) Assuming that you explicitly select the columns you need eg. SELECT [SalesOrderID],[SalesOrderDetailID], &#8230; (see question 1) what is the performance impact of adding an additional column to the view?</p>
<p>Best regards,<br />
Andreas</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Koko</title>
		<link>http://blog.sqlauthority.com/2010/08/26/sql-server-adding-column-is-expensive-limitation-of-the-views-part-2/#comment-121024</link>
		<dc:creator><![CDATA[Koko]]></dc:creator>
		<pubDate>Sun, 27 Feb 2011 18:42:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=9853#comment-121024</guid>
		<description><![CDATA[Interesting article. I&#039;m glad I found as I was about to make somewhat of a similar change.

I have a view consisting of 12 unions and all 12 unions join to customer table. I thought if I take the customer join outside the view and do 1 join to customer table the performance should be much better. Thinking logically joining once should be better than joining 12 times?

What do you guys think?]]></description>
		<content:encoded><![CDATA[<p>Interesting article. I&#8217;m glad I found as I was about to make somewhat of a similar change.</p>
<p>I have a view consisting of 12 unions and all 12 unions join to customer table. I thought if I take the customer join outside the view and do 1 join to customer table the performance should be much better. Thinking logically joining once should be better than joining 12 times?</p>
<p>What do you guys think?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: madhivanan</title>
		<link>http://blog.sqlauthority.com/2010/08/26/sql-server-adding-column-is-expensive-limitation-of-the-views-part-2/#comment-97118</link>
		<dc:creator><![CDATA[madhivanan]]></dc:creator>
		<pubDate>Mon, 01 Nov 2010 08:46:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=9853#comment-97118</guid>
		<description><![CDATA[example

Declare @var varchar(100)]]></description>
		<content:encoded><![CDATA[<p>example</p>
<p>Declare @var varchar(100)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kiran</title>
		<link>http://blog.sqlauthority.com/2010/08/26/sql-server-adding-column-is-expensive-limitation-of-the-views-part-2/#comment-96953</link>
		<dc:creator><![CDATA[kiran]]></dc:creator>
		<pubDate>Sun, 31 Oct 2010 11:43:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=9853#comment-96953</guid>
		<description><![CDATA[how declare varaible in store processure]]></description>
		<content:encoded><![CDATA[<p>how declare varaible in store processure</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SQL SERVER – View Over the View Not Possible with Index View – Limitations of the View 11 Journey to SQL Authority with Pinal Dave</title>
		<link>http://blog.sqlauthority.com/2010/08/26/sql-server-adding-column-is-expensive-limitation-of-the-views-part-2/#comment-89997</link>
		<dc:creator><![CDATA[SQL SERVER – View Over the View Not Possible with Index View – Limitations of the View 11 Journey to SQL Authority with Pinal Dave]]></dc:creator>
		<pubDate>Wed, 29 Sep 2010 01:30:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=9853#comment-89997</guid>
		<description><![CDATA[[...] 29, 2010 by pinaldave    When I wrote the article about SQL SERVER – Adding Column is Expensive by Joining Table Outside View – Limitation of the Vie..., I had received a comment that [...]]]></description>
		<content:encoded><![CDATA[<p>[...] 29, 2010 by pinaldave    When I wrote the article about SQL SERVER – Adding Column is Expensive by Joining Table Outside View – Limitation of the Vie&#8230;, I had received a comment that [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SQLAuthority News – A Monthly Round Up of SQLAuthority Blog Posts – August 2010 Journey to SQL Authority with Pinal Dave</title>
		<link>http://blog.sqlauthority.com/2010/08/26/sql-server-adding-column-is-expensive-limitation-of-the-views-part-2/#comment-85706</link>
		<dc:creator><![CDATA[SQLAuthority News – A Monthly Round Up of SQLAuthority Blog Posts – August 2010 Journey to SQL Authority with Pinal Dave]]></dc:creator>
		<pubDate>Tue, 31 Aug 2010 01:31:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=9853#comment-85706</guid>
		<description><![CDATA[[...] SQL SERVER – Adding Column is Expensive by Joining Table Outside View – Limitation of the Vie... [...]]]></description>
		<content:encoded><![CDATA[<p>[...] SQL SERVER – Adding Column is Expensive by Joining Table Outside View – Limitation of the Vie&#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Serene Tiger</title>
		<link>http://blog.sqlauthority.com/2010/08/26/sql-server-adding-column-is-expensive-limitation-of-the-views-part-2/#comment-85642</link>
		<dc:creator><![CDATA[Serene Tiger]]></dc:creator>
		<pubDate>Mon, 30 Aug 2010 11:25:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=9853#comment-85642</guid>
		<description><![CDATA[It may add overhead to add the column outside the view, but using the view consumes far less processing time.  I just rewrote a stored procedure that was taking 27 minutes to execute.  I created a schema-bound view, which I joined to another view in the sproc.  The query now executes in 6 minutes.]]></description>
		<content:encoded><![CDATA[<p>It may add overhead to add the column outside the view, but using the view consumes far less processing time.  I just rewrote a stored procedure that was taking 27 minutes to execute.  I created a schema-bound view, which I joined to another view in the sproc.  The query now executes in 6 minutes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marko Parkkola</title>
		<link>http://blog.sqlauthority.com/2010/08/26/sql-server-adding-column-is-expensive-limitation-of-the-views-part-2/#comment-85320</link>
		<dc:creator><![CDATA[Marko Parkkola]]></dc:creator>
		<pubDate>Thu, 26 Aug 2010 09:02:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=9853#comment-85320</guid>
		<description><![CDATA[I&#039;ve tried to phrase this comments couple of times and I still isn&#039;t exactly what I wanted to say so I&#039;ll just post it and ask if you don&#039;t understand something :)


Views and especially schemabound views has one upside which is ironically quite the opposite what&#039;s this article about.

When I create schemabound view it&#039;ll force me to make sure that:

a) I&#039;ve thought about the situation that understand what I&#039;m doing
b) Later on, if I need to alter table schema schemabinding makes sure that I can&#039;t do things that&#039;ll break lots of things up

So if I suddenly realize that I need to add some column to my query, which is not in the view, I need to think that is this what I really want and need. Is this something one time only or is it something that is used a lot? 

If former I&#039;ll just make ad-hoc query and be done with it.

But if latter I&#039;ll add the column to the view. DB then goes and creates execution plans and statistics for the changed view and possibly optimizes execution plan and speeds up the query.]]></description>
		<content:encoded><![CDATA[<p>I&#8217;ve tried to phrase this comments couple of times and I still isn&#8217;t exactly what I wanted to say so I&#8217;ll just post it and ask if you don&#8217;t understand something :)</p>
<p>Views and especially schemabound views has one upside which is ironically quite the opposite what&#8217;s this article about.</p>
<p>When I create schemabound view it&#8217;ll force me to make sure that:</p>
<p>a) I&#8217;ve thought about the situation that understand what I&#8217;m doing<br />
b) Later on, if I need to alter table schema schemabinding makes sure that I can&#8217;t do things that&#8217;ll break lots of things up</p>
<p>So if I suddenly realize that I need to add some column to my query, which is not in the view, I need to think that is this what I really want and need. Is this something one time only or is it something that is used a lot? </p>
<p>If former I&#8217;ll just make ad-hoc query and be done with it.</p>
<p>But if latter I&#8217;ll add the column to the view. DB then goes and creates execution plans and statistics for the changed view and possibly optimizes execution plan and speeds up the query.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sumit Thapar</title>
		<link>http://blog.sqlauthority.com/2010/08/26/sql-server-adding-column-is-expensive-limitation-of-the-views-part-2/#comment-85291</link>
		<dc:creator><![CDATA[Sumit Thapar]]></dc:creator>
		<pubDate>Thu, 26 Aug 2010 04:11:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=9853#comment-85291</guid>
		<description><![CDATA[Nice article sir....thank you...i did not know that before.....]]></description>
		<content:encoded><![CDATA[<p>Nice article sir&#8230;.thank you&#8230;i did not know that before&#8230;..</p>
]]></content:encoded>
	</item>
</channel>
</rss>
