<?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: SEQUENCE in SQL Server 2012</title>
	<atom:link href="http://www.sql-server-performance.com/2011/sequence-sql-server-2011/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sql-server-performance.com/2011/sequence-sql-server-2011/</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: Chris</title>
		<link>http://www.sql-server-performance.com/2011/sequence-sql-server-2011/#comment-2440</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Thu, 22 Nov 2012 09:21:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?=1916#comment-2440</guid>
		<description><![CDATA[It is very useful in ORM based applications where you need to know what is the ID of saved entity before commiting the transaction.]]></description>
		<content:encoded><![CDATA[<p>It is very useful in ORM based applications where you need to know what is the ID of saved entity before commiting the transaction.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jtautry</title>
		<link>http://www.sql-server-performance.com/2011/sequence-sql-server-2011/#comment-1828</link>
		<dc:creator>jtautry</dc:creator>
		<pubDate>Fri, 13 Apr 2012 17:18:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?=1916#comment-1828</guid>
		<description><![CDATA[One scenario that I can think of is to coordinate identity values across multiple tables.  If you have a parent table with two child tables for example, you would normally insert the parent rec, return the identity value, then insert the child rec.  However, if the only reason the parent table exists is to make sure the child IDs are unique, you could use a sequence instead and get rid of the overhead of the parent table.
Not sure if this is practical or not, just the first thing that came to mind.]]></description>
		<content:encoded><![CDATA[<p>One scenario that I can think of is to coordinate identity values across multiple tables.  If you have a parent table with two child tables for example, you would normally insert the parent rec, return the identity value, then insert the child rec.  However, if the only reason the parent table exists is to make sure the child IDs are unique, you could use a sequence instead and get rid of the overhead of the parent table.</p>
<p>Not sure if this is practical or not, just the first thing that came to mind.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: paritosh</title>
		<link>http://www.sql-server-performance.com/2011/sequence-sql-server-2011/#comment-1823</link>
		<dc:creator>paritosh</dc:creator>
		<pubDate>Wed, 11 Apr 2012 10:38:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?=1916#comment-1823</guid>
		<description><![CDATA[Nice article , Except performance why I would use this function?
any practical Scene in which i can see the usage.]]></description>
		<content:encoded><![CDATA[<p>Nice article , Except performance why I would use this function?</p>
<p>any practical Scene in which i can see the usage.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
