<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.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>Partial Aggregation</title><link>http://blogs.msdn.com/craigfr/archive/2008/01/18/partial-aggregation.aspx</link><description>In some of my past posts, I've discussed how SQL Server implements aggregation including the stream aggregate and hash aggregate operators. I also used hash aggregation as an initial example in my introductory post on parallel query execution . In this</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Table Variable vs Parallelism</title><link>http://blogs.msdn.com/craigfr/archive/2008/01/18/partial-aggregation.aspx#8397706</link><pubDate>Tue, 15 Apr 2008 18:01:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8397706</guid><dc:creator>EXEC dbo.LongTermMemory__Archive</dc:creator><description>&lt;p&gt;There are many myths surrounding table variables and one of the most common is probably the 'in memory'&lt;/p&gt;
</description></item></channel></rss>