<?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>Random Prefetching</title><link>http://blogs.msdn.com/craigfr/archive/2008/10/07/random-prefetching.aspx</link><description>In my last post , I explained the importance of asynchronous I/O and described how SQL Server uses sequential read ahead to boost the performance of scans. In this post, I'll discuss how SQL Server uses random prefetching. Let's begin with a simple example</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>OPTIMIZED Nested Loops Joins</title><link>http://blogs.msdn.com/craigfr/archive/2008/10/07/random-prefetching.aspx#9486999</link><pubDate>Wed, 18 Mar 2009 17:43:47 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9486999</guid><dc:creator>Craig Freedman's SQL Server Blog</dc:creator><description>&lt;p&gt;In my past two posts, I explained how SQL Server may add a sort to the outer side of a nested loops join&lt;/p&gt;
</description></item></channel></rss>