<?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>Probe Residual when you have a Hash Match – a hidden cost in execution plans</title><link>http://sqlblog.com/blogs/rob_farley/archive/2011/03/22/probe-residual-when-you-have-a-hash-match-a-hidden-cost-in-execution-plans.aspx</link><description>No, this post has nothing to do with airport security, and nothing to do with marijuana. Being honest, this post is only half about Hash Matches and Probe Residuals. It’s more about the types of predicates you can see mentioned in a SQL Server Execution</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP2 (Build: 61129.1)</generator><item><title>The power of T-SQL's APPLY operator</title><link>http://sqlblog.com/blogs/rob_farley/archive/2011/03/22/probe-residual-when-you-have-a-hash-match-a-hidden-cost-in-execution-plans.aspx#34846</link><pubDate>Tue, 12 Apr 2011 23:30:13 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:34846</guid><dc:creator>Rob Farley</dc:creator><description>&lt;p&gt;I could go on all day about APPLY – it really is an incredible part of T-SQL. It helps solves problems&lt;/p&gt;
</description></item><item><title>LobsterPot submissions for SQLPASS</title><link>http://sqlblog.com/blogs/rob_farley/archive/2011/03/22/probe-residual-when-you-have-a-hash-match-a-hidden-cost-in-execution-plans.aspx#35496</link><pubDate>Fri, 06 May 2011 04:05:43 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:35496</guid><dc:creator>Rob Farley</dc:creator><description>&lt;p&gt;My guys are great! When PASS started accepting abstract submissions for their Summit (in October this&lt;/p&gt;
</description></item><item><title>Join Performance, Implicit Conversions, and Residuals</title><link>http://sqlblog.com/blogs/rob_farley/archive/2011/03/22/probe-residual-when-you-have-a-hash-match-a-hidden-cost-in-execution-plans.aspx#37053</link><pubDate>Tue, 19 Jul 2011 01:06:04 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:37053</guid><dc:creator>Paul White: Page Free Space</dc:creator><description>&lt;p&gt;You probably already know that it’s important to be aware of data types when writing queries, and that&lt;/p&gt;
</description></item><item><title>re: Probe Residual when you have a Hash Match – a hidden cost in execution plans</title><link>http://sqlblog.com/blogs/rob_farley/archive/2011/03/22/probe-residual-when-you-have-a-hash-match-a-hidden-cost-in-execution-plans.aspx#46406</link><pubDate>Tue, 27 Nov 2012 08:41:28 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:46406</guid><dc:creator>Chris Adkin</dc:creator><description>&lt;p&gt;Presumably the use of filter indexes might be another option for solving this problem ?&lt;/p&gt;</description></item><item><title>re: Probe Residual when you have a Hash Match – a hidden cost in execution plans</title><link>http://sqlblog.com/blogs/rob_farley/archive/2011/03/22/probe-residual-when-you-have-a-hash-match-a-hidden-cost-in-execution-plans.aspx#46407</link><pubDate>Tue, 27 Nov 2012 08:45:53 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:46407</guid><dc:creator>Rob Farley</dc:creator><description>&lt;p&gt;Yes - but this post is more designed for highlighting the issue. I figure that solving it is a standard exercise in query tuning, once you see the impact of the Residuality.&lt;/p&gt;
</description></item></channel></rss>