<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: How to Perform SQL Server Row-by-Row Operations Without Cursors</title>
	<atom:link href="http://www.sql-server-performance.com/2004/operations-no-cursors/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sql-server-performance.com/2004/operations-no-cursors/</link>
	<description>SQL Server Performance Tuning</description>
	<lastBuildDate>Fri, 17 May 2013 13:31:24 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Jeff Moden</title>
		<link>http://www.sql-server-performance.com/2004/operations-no-cursors/#comment-3233</link>
		<dc:creator>Jeff Moden</dc:creator>
		<pubDate>Sun, 10 Mar 2013 06:04:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?=375#comment-3233</guid>
		<description><![CDATA[There&#039;s lots of claims of performance in this article but no substantial evidence that the Temp Table/While Loop replacement for the Cursor is any faster.  A well written &quot;firehose&quot; cursor will usually beat a well written Temp Table/While loop combination.
Yes, cursors are usually a bad thing and should be avoided but only if you can come up with a proper set-based solution.  That goes for any form of RBAR including Temp Tables/While loops and recursive CTEs.]]></description>
		<content:encoded><![CDATA[<p>There&#8217;s lots of claims of performance in this article but no substantial evidence that the Temp Table/While Loop replacement for the Cursor is any faster.  A well written &#8220;firehose&#8221; cursor will usually beat a well written Temp Table/While loop combination.</p>
<p>Yes, cursors are usually a bad thing and should be avoided but only if you can come up with a proper set-based solution.  That goes for any form of RBAR including Temp Tables/While loops and recursive CTEs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Toqeer</title>
		<link>http://www.sql-server-performance.com/2004/operations-no-cursors/#comment-523</link>
		<dc:creator>Toqeer</dc:creator>
		<pubDate>Wed, 17 Aug 2011 05:16:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?=375#comment-523</guid>
		<description><![CDATA[The following are the techniques which can be used instead of cursors:
1. CTE
2. Loop
3. Temporary Tables]]></description>
		<content:encoded><![CDATA[<p>The following are the techniques which can be used instead of cursors:</p>
<p>1. CTE<br />
2. Loop<br />
3. Temporary Tables</p>
]]></content:encoded>
	</item>
</channel>
</rss>
