<?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>Execution Plan Analysis: The Mystery Work Table</title><link>http://sqlblog.com/blogs/paul_white/archive/2013/03/08/execution-plan-analysis-the-mystery-work-table.aspx</link><description>I love SQL Server execution plans. It is often easy to spot the cause of a performance problem just by looking at one. The task is considerably easier if the plan includes run-time information (a so-called ‘actual’ execution plan), but even a compiled</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP2 (Build: 61129.1)</generator><item><title>re: Execution Plan Analysis: The Mystery Work Table</title><link>http://sqlblog.com/blogs/paul_white/archive/2013/03/08/execution-plan-analysis-the-mystery-work-table.aspx#48122</link><pubDate>Thu, 07 Mar 2013 22:16:52 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:48122</guid><dc:creator>mjswart</dc:creator><description>&lt;p&gt;Well done Paul, I always like these in depth posts of yours. The time spent running through the examples always pays off. &lt;/p&gt;
&lt;p&gt;There's a lot of things going on here to make this issue occur. There's the nested loops prefetching, the manufactured lobs etc... &lt;/p&gt;
&lt;p&gt;I like to put myself in the position of a DBA who's asked to look at this query. To be honest I don't think I'd be up to the task of understanding the exact cause without a humungous amount of mental effort (so good on you).&lt;/p&gt;
&lt;p&gt;But I like to think that maybe some knee-jerk rules of thumb I exercise might have done the trick: Concatenating strings in the app for example.&lt;/p&gt;
&lt;p&gt;But thanks again for the write up! Your internals posts are always fascinating.&lt;/p&gt;</description></item><item><title>re: Execution Plan Analysis: The Mystery Work Table</title><link>http://sqlblog.com/blogs/paul_white/archive/2013/03/08/execution-plan-analysis-the-mystery-work-table.aspx#48123</link><pubDate>Thu, 07 Mar 2013 22:22:31 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:48123</guid><dc:creator>Alejandro Mesa</dc:creator><description>&lt;p&gt;A delightful reading!&lt;/p&gt;
&lt;p&gt;Adam, could you add the &amp;quot;Like&amp;quot; button?&lt;/p&gt;
&lt;p&gt;--&lt;/p&gt;
&lt;p&gt;AMB&lt;/p&gt;</description></item><item><title>re: Execution Plan Analysis: The Mystery Work Table</title><link>http://sqlblog.com/blogs/paul_white/archive/2013/03/08/execution-plan-analysis-the-mystery-work-table.aspx#48124</link><pubDate>Thu, 07 Mar 2013 22:50:21 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:48124</guid><dc:creator>Paul White</dc:creator><description>&lt;p&gt;Hi Michael,&lt;/p&gt;
&lt;p&gt;I agree, though in this particular case, it turns out the string concatenation was to feed input to an in-query CLR function - a valid use case with only partial workarounds and alternatives AFAIK. Nevertheless, this was a fun post to write.&lt;/p&gt;
&lt;p&gt;Paul&lt;/p&gt;
&lt;p&gt;P.S. Cheers, Alejandro!&lt;/p&gt;
</description></item><item><title>re: Execution Plan Analysis: The Mystery Work Table</title><link>http://sqlblog.com/blogs/paul_white/archive/2013/03/08/execution-plan-analysis-the-mystery-work-table.aspx#48168</link><pubDate>Mon, 11 Mar 2013 05:37:14 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:48168</guid><dc:creator>SomewhereSomehow</dc:creator><description>&lt;p&gt;Very interesting detective story from the one hand, and useful informative reading from the other, thank you! &lt;/p&gt;
&lt;p&gt;Small question: &amp;quot;the logical reads reported on this work table indicate the number of rows&amp;quot; - curious note! Is it documented somewhere, or just an observation?&lt;/p&gt;</description></item><item><title>re: Execution Plan Analysis: The Mystery Work Table</title><link>http://sqlblog.com/blogs/paul_white/archive/2013/03/08/execution-plan-analysis-the-mystery-work-table.aspx#48169</link><pubDate>Mon, 11 Mar 2013 06:21:07 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:48169</guid><dc:creator>Paul White</dc:creator><description>&lt;p&gt;Hi Dima,&lt;/p&gt;
&lt;p&gt;More details at &lt;a rel="nofollow" target="_new" href="http://stackoverflow.com/questions/4230838/why-are-logical-reads-for-windowed-aggregate-functions-so-high"&gt;http://stackoverflow.com/questions/4230838/why-are-logical-reads-for-windowed-aggregate-functions-so-high&lt;/a&gt; and &lt;a rel="nofollow" target="_new" href="http://sqlblog.com/blogs/paul_white/archive/2010/07/28/partitioning-and-the-common-subexpression-spool.aspx"&gt;http://sqlblog.com/blogs/paul_white/archive/2010/07/28/partitioning-and-the-common-subexpression-spool.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;As far as being documented or not - depends: it is mentioned in a book somewhere - I think the author might have been Craig Freedman, I'm afraid I don't recall more than that.&lt;/p&gt;
</description></item><item><title>re: Execution Plan Analysis: The Mystery Work Table</title><link>http://sqlblog.com/blogs/paul_white/archive/2013/03/08/execution-plan-analysis-the-mystery-work-table.aspx#48174</link><pubDate>Mon, 11 Mar 2013 08:40:10 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:48174</guid><dc:creator>SomewhereSomehow</dc:creator><description>&lt;p&gt;Anyway, that's interesting. Thanks for the links!&lt;/p&gt;</description></item><item><title>re: Execution Plan Analysis: The Mystery Work Table</title><link>http://sqlblog.com/blogs/paul_white/archive/2013/03/08/execution-plan-analysis-the-mystery-work-table.aspx#48531</link><pubDate>Thu, 04 Apr 2013 13:09:01 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:48531</guid><dc:creator>John Waclawski</dc:creator><description>&lt;p&gt;Great, great information!! &amp;nbsp; Thank you!! &lt;/p&gt;
&lt;p&gt;Is there anyway to repost this information not using SQL Sentry because some of us can't afford to buy the software &amp;amp; would rather use what is available to us. &amp;nbsp;Unless the free version gives us the same information.&lt;/p&gt;
&lt;p&gt;Thank you again!!&lt;/p&gt;</description></item><item><title>re: Execution Plan Analysis: The Mystery Work Table</title><link>http://sqlblog.com/blogs/paul_white/archive/2013/03/08/execution-plan-analysis-the-mystery-work-table.aspx#48770</link><pubDate>Wed, 17 Apr 2013 23:37:21 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:48770</guid><dc:creator>Paul White</dc:creator><description>&lt;p&gt;Hi John,&lt;/p&gt;
&lt;p&gt;The free version is all that is required to reproduce the screenshots in this post. I do prefer to use P/E for blog work because if nothing else the graphical plans fit better in the space available. As you can see, there are other benefits in the way it presents information too.&lt;/p&gt;
&lt;p&gt;I do offer a full refund to anyone not happy with the way I write my blog posts of course :-p&lt;/p&gt;
</description></item></channel></rss>