<?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; Outer Join in Indexed View &#8211; Question to Readers</title>
	<atom:link href="http://blog.sqlauthority.com/2009/09/25/sql-server-outer-join-in-indexed-view-question-to-readers/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.sqlauthority.com/2009/09/25/sql-server-outer-join-in-indexed-view-question-to-readers/</link>
	<description>Personal Notes of Pinal Dave</description>
	<lastBuildDate>Sun, 12 Feb 2012 09:22:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Ringo Schplingo</title>
		<link>http://blog.sqlauthority.com/2009/09/25/sql-server-outer-join-in-indexed-view-question-to-readers/#comment-190788</link>
		<dc:creator><![CDATA[Ringo Schplingo]]></dc:creator>
		<pubDate>Tue, 08 Nov 2011 11:28:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=6910#comment-190788</guid>
		<description><![CDATA[To me this makes little sense, an outer join is LESS LIKELY to make rows disappear from a recordset as it is less restrictive. For example if I inner join from say a fact table to a dimension table, should the dimension table not contain all values which are in the fact table, then not all rows which are in the fact table will be returned, whereas using a left join from the fact table will ensure that all results are returned!]]></description>
		<content:encoded><![CDATA[<p>To me this makes little sense, an outer join is LESS LIKELY to make rows disappear from a recordset as it is less restrictive. For example if I inner join from say a fact table to a dimension table, should the dimension table not contain all values which are in the fact table, then not all rows which are in the fact table will be returned, whereas using a left join from the fact table will ensure that all results are returned!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SQL SERVER – Interview Questions and Answers – Frequently Asked Questions – Day 5 of 31 Journey to SQLAuthority</title>
		<link>http://blog.sqlauthority.com/2009/09/25/sql-server-outer-join-in-indexed-view-question-to-readers/#comment-145990</link>
		<dc:creator><![CDATA[SQL SERVER – Interview Questions and Answers – Frequently Asked Questions – Day 5 of 31 Journey to SQLAuthority]]></dc:creator>
		<pubDate>Tue, 05 Jul 2011 01:32:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=6910#comment-145990</guid>
		<description><![CDATA[[...] Rows can logically disappear from an indexed view based on OUTER JOIN when you insert data into a base table. This makes incrementally updating OUTER JOIN views relatively complex to implement, and the performance of the implementation would be slower than for views based on standard (INNER) JOIN.(Read More Here) [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Rows can logically disappear from an indexed view based on OUTER JOIN when you insert data into a base table. This makes incrementally updating OUTER JOIN views relatively complex to implement, and the performance of the implementation would be slower than for views based on standard (INNER) JOIN.(Read More Here) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dikshith</title>
		<link>http://blog.sqlauthority.com/2009/09/25/sql-server-outer-join-in-indexed-view-question-to-readers/#comment-59366</link>
		<dc:creator><![CDATA[dikshith]]></dc:creator>
		<pubDate>Tue, 05 Jan 2010 13:05:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=6910#comment-59366</guid>
		<description><![CDATA[good tutorials....! continue with the blogs so that will be helpful for developers.]]></description>
		<content:encoded><![CDATA[<p>good tutorials&#8230;.! continue with the blogs so that will be helpful for developers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chintak Chhapia</title>
		<link>http://blog.sqlauthority.com/2009/09/25/sql-server-outer-join-in-indexed-view-question-to-readers/#comment-56176</link>
		<dc:creator><![CDATA[Chintak Chhapia]]></dc:creator>
		<pubDate>Fri, 25 Sep 2009 19:43:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=6910#comment-56176</guid>
		<description><![CDATA[One the situion is like this.
When we have two tables, one for list of employee and the second one the list of retired employee.

then the rows from following query disppear when we add record in retired table 

select e.id	,e.name 
from dbo.employee e
left join RetiredEmployee j on e.id=j.id
where j.id is null]]></description>
		<content:encoded><![CDATA[<p>One the situion is like this.<br />
When we have two tables, one for list of employee and the second one the list of retired employee.</p>
<p>then the rows from following query disppear when we add record in retired table </p>
<p>select e.id	,e.name<br />
from dbo.employee e<br />
left join RetiredEmployee j on e.id=j.id<br />
where j.id is null</p>
]]></content:encoded>
	</item>
</channel>
</rss>

