<?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>Increase your SQL Server performance by replacing cursors with set operations</title><link>http://blogs.msdn.com/mssqlisv/archive/2008/03/18/increase-your-sql-server-performance-by-replacing-cursors-with-set-operations.aspx</link><description>You have probably heard many times, from different sources, that as a best practice; avoid using TSQL cursors. During a recent visit to a partner we ran into a common cursor case, which I wanted to use as an example to demonstrate why you should avoid</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>MSDN Blog Postings  &amp;raquo; Increase your SQL Server performance by replacing cursors with set operations</title><link>http://blogs.msdn.com/mssqlisv/archive/2008/03/18/increase-your-sql-server-performance-by-replacing-cursors-with-set-operations.aspx#8324382</link><pubDate>Wed, 19 Mar 2008 04:33:32 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8324382</guid><dc:creator>MSDN Blog Postings  » Increase your SQL Server performance by replacing cursors with set operations</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://msdnrss.thecoderblogs.com/2008/03/18/increase-your-sql-server-performance-by-replacing-cursors-with-set-operations/"&gt;http://msdnrss.thecoderblogs.com/2008/03/18/increase-your-sql-server-performance-by-replacing-cursors-with-set-operations/&lt;/a&gt;&lt;/p&gt;
</description></item></channel></rss>