<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://sqlblog.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Run-time Execution Plan Options</title><link>http://sqlblog.com/blogs/joe_chang/archive/2009/02/21/run-time-execution-plan-options.aspx</link><description>What are the top core SQL Server engine performance issues today, after all the improvements that have gone into 2005 and 2008? (I am excluding matters beyond the power of Microsoft, like eliminating bad developers.) SQL Server already has statement level</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP2 (Build: 61129.1)</generator><item><title>re: Run-time Execution Plan Options</title><link>http://sqlblog.com/blogs/joe_chang/archive/2009/02/21/run-time-execution-plan-options.aspx#12074</link><pubDate>Sun, 22 Feb 2009 02:32:17 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:12074</guid><dc:creator>Alexander Kuznetsov</dc:creator><description>&lt;p&gt;Joe,&lt;/p&gt;
&lt;p&gt;It's a great post! Can you change the third tag from Query Hinys to Query Hings?&lt;/p&gt;
</description></item><item><title>re: Run-time Execution Plan Options</title><link>http://sqlblog.com/blogs/joe_chang/archive/2009/02/21/run-time-execution-plan-options.aspx#12107</link><pubDate>Mon, 23 Feb 2009 15:45:23 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:12107</guid><dc:creator>noeldr</dc:creator><description>&lt;p&gt;&amp;quot;SQL Server already has statement level recompile for multi-statement stored procedures.&amp;quot; Yeah, which is BUGGY! Watch out for that: &lt;a rel="nofollow" target="_new" href="https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=386810"&gt;https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=386810&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>re: Run-time Execution Plan Options</title><link>http://sqlblog.com/blogs/joe_chang/archive/2009/02/21/run-time-execution-plan-options.aspx#12254</link><pubDate>Thu, 26 Feb 2009 15:22:57 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:12254</guid><dc:creator>jchang</dc:creator><description>&lt;p&gt;ok, this just jogged my memory, last year I saw an application, where the stored procedures, instead of writing a simple query joining several tables, had one table valued function that joined to the remaining tables.&lt;/p&gt;
&lt;p&gt;I think this over came the problem of the stored procedure picking up inconsistent parameters on compile. For their particular case, a simple WITH RECOMPILE on the stored procedure seemed to be the best solution as the compile cost was low in relation to what could be afforded for the stored procedure, even when few rows are affected. I assume MS will eventually debug this, but always verify and consider alternatives. &lt;/p&gt;
</description></item></channel></rss>