<?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 Optimizer Hint ROBUST PLAN &#8211; Question to You</title>
	<atom:link href="http://blog.sqlauthority.com/2009/06/15/sql-server-query-optimizer-hint-robust-plan-question-to-you/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.sqlauthority.com/2009/06/15/sql-server-query-optimizer-hint-robust-plan-question-to-you/</link>
	<description>Personal Notes of Pinal Dave</description>
	<lastBuildDate>Fri, 17 May 2013 15:26:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: MikeZane</title>
		<link>http://blog.sqlauthority.com/2009/06/15/sql-server-query-optimizer-hint-robust-plan-question-to-you/#comment-53701</link>
		<dc:creator><![CDATA[MikeZane]]></dc:creator>
		<pubDate>Tue, 14 Jul 2009 18:09:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=5467#comment-53701</guid>
		<description><![CDATA[Here is a query that we use:

Select 
HeaderText = v.CombinedText, 
Text1 = t1.CombinedText, 
Text2 = Convert(char(6000), t2.CombinedText), 
Text3 = Convert(char(6000), t3.CombinedText), 
Text4 = Convert(char(7401), t4.CombinedText)
from vw_OnlineExport_Form v
Inner Join tmpResponseConvert1 t1 on t1.SurveyNumber = v.SurveyNumber
Inner Join tmpResponseConvert2 t2 on t2.SurveyNumber = v.SurveyNumber
Inner Join tmpResponseConvert3 t3 on t3.SurveyNumber = v.SurveyNumber
Inner Join tmpResponseConvert4 t4 on t4.SurveyNumber = v.SurveyNumber
OPTION (ROBUST PLAN)

Our sql system needs to convert data that is full of verbatim comments that are stored in a vertical format to a horizontal fixed length format.  We do this by building records of 6000-7500 characters each and join them all together as you see above.  The end result is an output fixed file of 22500.]]></description>
		<content:encoded><![CDATA[<p>Here is a query that we use:</p>
<p>Select<br />
HeaderText = v.CombinedText,<br />
Text1 = t1.CombinedText,<br />
Text2 = Convert(char(6000), t2.CombinedText),<br />
Text3 = Convert(char(6000), t3.CombinedText),<br />
Text4 = Convert(char(7401), t4.CombinedText)<br />
from vw_OnlineExport_Form v<br />
Inner Join tmpResponseConvert1 t1 on t1.SurveyNumber = v.SurveyNumber<br />
Inner Join tmpResponseConvert2 t2 on t2.SurveyNumber = v.SurveyNumber<br />
Inner Join tmpResponseConvert3 t3 on t3.SurveyNumber = v.SurveyNumber<br />
Inner Join tmpResponseConvert4 t4 on t4.SurveyNumber = v.SurveyNumber<br />
OPTION (ROBUST PLAN)</p>
<p>Our sql system needs to convert data that is full of verbatim comments that are stored in a vertical format to a horizontal fixed length format.  We do this by building records of 6000-7500 characters each and join them all together as you see above.  The end result is an output fixed file of 22500.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mycall</title>
		<link>http://blog.sqlauthority.com/2009/06/15/sql-server-query-optimizer-hint-robust-plan-question-to-you/#comment-53208</link>
		<dc:creator><![CDATA[mycall]]></dc:creator>
		<pubDate>Tue, 23 Jun 2009 19:54:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=5467#comment-53208</guid>
		<description><![CDATA[When in doubt, consult the source:

ROBUST PLAN 
Forces the query optimizer to try a plan that works for the maximum potential row size, possibly at the expense of performance. When the query is processed, intermediate tables and operators may have to store and process rows that are wider than any one of the input rows. The rows may be so wide that, sometimes, the particular operator cannot process the row. If this occurs, the Database Engine produces an error during query execution. By using ROBUST PLAN, you instruct the query optimizer not to consider any query plans that may encounter this problem.

If such a plan is not possible, the query optimizer returns an error instead of deferring error detection to query execution. Rows may contain variable-length columns; the Database Engine allows for rows to be defined that have a maximum potential size beyond the ability of the Database Engine to process them. Generally, despite the maximum potential 

http://social.msdn.microsoft.com/Forums/en-US/sqlgetstarted/thread/12f66b30-6a46-41f0-9a7c-3690f5ddb538/

http://social.msdn.microsoft.com/Forums/en-US/transactsql/thread/c07f1ad3-4080-4f84-8672-88312c8b24f6/

http://social.msdn.microsoft.com/Forums/en-US/transactsql/thread/c07f1ad3-4080-4f84-8672-88312c8b24f6/]]></description>
		<content:encoded><![CDATA[<p>When in doubt, consult the source:</p>
<p>ROBUST PLAN<br />
Forces the query optimizer to try a plan that works for the maximum potential row size, possibly at the expense of performance. When the query is processed, intermediate tables and operators may have to store and process rows that are wider than any one of the input rows. The rows may be so wide that, sometimes, the particular operator cannot process the row. If this occurs, the Database Engine produces an error during query execution. By using ROBUST PLAN, you instruct the query optimizer not to consider any query plans that may encounter this problem.</p>
<p>If such a plan is not possible, the query optimizer returns an error instead of deferring error detection to query execution. Rows may contain variable-length columns; the Database Engine allows for rows to be defined that have a maximum potential size beyond the ability of the Database Engine to process them. Generally, despite the maximum potential </p>
<p><a href="http://social.msdn.microsoft.com/Forums/en-US/sqlgetstarted/thread/12f66b30-6a46-41f0-9a7c-3690f5ddb538/" rel="nofollow">http://social.msdn.microsoft.com/Forums/en-US/sqlgetstarted/thread/12f66b30-6a46-41f0-9a7c-3690f5ddb538/</a></p>
<p><a href="http://social.msdn.microsoft.com/Forums/en-US/transactsql/thread/c07f1ad3-4080-4f84-8672-88312c8b24f6/" rel="nofollow">http://social.msdn.microsoft.com/Forums/en-US/transactsql/thread/c07f1ad3-4080-4f84-8672-88312c8b24f6/</a></p>
<p><a href="http://social.msdn.microsoft.com/Forums/en-US/transactsql/thread/c07f1ad3-4080-4f84-8672-88312c8b24f6/" rel="nofollow">http://social.msdn.microsoft.com/Forums/en-US/transactsql/thread/c07f1ad3-4080-4f84-8672-88312c8b24f6/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Tkatck</title>
		<link>http://blog.sqlauthority.com/2009/06/15/sql-server-query-optimizer-hint-robust-plan-question-to-you/#comment-53028</link>
		<dc:creator><![CDATA[Brian Tkatck]]></dc:creator>
		<pubDate>Mon, 15 Jun 2009 17:48:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=5467#comment-53028</guid>
		<description><![CDATA[Sheesh, searching for this error brings up your article on many different websites. :)]]></description>
		<content:encoded><![CDATA[<p>Sheesh, searching for this error brings up your article on many different websites. :)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
