<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>SQL Server Planet</title>
	<atom:link href="http://sqlserverplanet.com/feed" rel="self" type="application/rss+xml" />
	<link>http://sqlserverplanet.com</link>
	<description>Tips and Articles on SQL Server</description>
	<lastBuildDate>Tue, 31 Jan 2012 01:33:18 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Avoiding IF.. ELSE by using WHERE EXISTS</title>
		<link>http://sqlserverplanet.com/tsql/avoiding-if-else-by-using-where-exists</link>
		<comments>http://sqlserverplanet.com/tsql/avoiding-if-else-by-using-where-exists#comments</comments>
		<pubDate>Sun, 29 Jan 2012 19:58:06 +0000</pubDate>
		<dc:creator>Derek Dieter</dc:creator>
				<category><![CDATA[Concurrency]]></category>
		<category><![CDATA[TSQL]]></category>

		<guid isPermaLink="false">http://sqlserverplanet.com/?p=2284</guid>
		<description><![CDATA[When coming from a programming background, it&#8217;s natural to want to frame conditional operations within the familiar if.. else constructs. This happens in a lot of SQL code I have worked with (and I used to be a contributor also). The technique below is based on a common scenario. Say you want to insert new [...]]]></description>
		<wfw:commentRss>http://sqlserverplanet.com/tsql/avoiding-if-else-by-using-where-exists/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>DROP INDEX SYNTAX</title>
		<link>http://sqlserverplanet.com/tsql/drop-index-syntax</link>
		<comments>http://sqlserverplanet.com/tsql/drop-index-syntax#comments</comments>
		<pubDate>Sun, 29 Jan 2012 19:05:14 +0000</pubDate>
		<dc:creator>Derek Dieter</dc:creator>
				<category><![CDATA[TSQL]]></category>

		<guid isPermaLink="false">http://sqlserverplanet.com/?p=2280</guid>
		<description><![CDATA[Here is the syntax needed in order to drop a single index: USE YourDatabaseName; DROP INDEX IX_Product_1 ON dbo.Product; You can also drop multiple indexes within a single transaction: USE YourDatabaseName; DROP INDEX IX_Product_1 ON dbo.Product, IX_Customer_1 ON dbo.Customer; Permissions The permissions needed to drop an index are alter permissions to the table. This is [...]]]></description>
		<wfw:commentRss>http://sqlserverplanet.com/tsql/drop-index-syntax/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SET TRANSACTION ISOLATION LEVEL</title>
		<link>http://sqlserverplanet.com/tsql/set-transaction-isolation-level</link>
		<comments>http://sqlserverplanet.com/tsql/set-transaction-isolation-level#comments</comments>
		<pubDate>Sun, 29 Jan 2012 18:10:35 +0000</pubDate>
		<dc:creator>Derek Dieter</dc:creator>
				<category><![CDATA[Concurrency]]></category>
		<category><![CDATA[TSQL]]></category>

		<guid isPermaLink="false">http://sqlserverplanet.com/?p=2277</guid>
		<description><![CDATA[This statement is used to set the isolation level for either a connection or a stored procedure. The most typical use I&#8217;ve seen is at the top of a stored procedure in order to avoid locking and deadlocks. This is a cleaner alternative to using WITH (NOLOCK) hints on tables. If you set the isolation [...]]]></description>
		<wfw:commentRss>http://sqlserverplanet.com/tsql/set-transaction-isolation-level/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to Create a Type2 SCD (Slowly Changing Dimension)</title>
		<link>http://sqlserverplanet.com/data-warehouse/how-to-create-a-type2-scd-slowly-changing-dimension</link>
		<comments>http://sqlserverplanet.com/data-warehouse/how-to-create-a-type2-scd-slowly-changing-dimension#comments</comments>
		<pubDate>Tue, 15 Nov 2011 05:53:22 +0000</pubDate>
		<dc:creator>Derek Dieter</dc:creator>
				<category><![CDATA[Data Warehouse]]></category>

		<guid isPermaLink="false">http://sqlserverplanet.com/?p=2248</guid>
		<description><![CDATA[This article could just as well be called creating a historical snapshot table. This type of table is also referenced as a dimension depending on what kind of data repository it&#8217;s located in. Personally, I prefer to keep a historical snapshot table in a normalized data store that contains history. This normalized data store is [...]]]></description>
		<wfw:commentRss>http://sqlserverplanet.com/data-warehouse/how-to-create-a-type2-scd-slowly-changing-dimension/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Using DBCC CHECKIDENT to Reseed a Table After Delete</title>
		<link>http://sqlserverplanet.com/tsql/using-dbcc-checkident-to-reseed-a-table-after-delete</link>
		<comments>http://sqlserverplanet.com/tsql/using-dbcc-checkident-to-reseed-a-table-after-delete#comments</comments>
		<pubDate>Sun, 13 Nov 2011 23:56:39 +0000</pubDate>
		<dc:creator>Derek Dieter</dc:creator>
				<category><![CDATA[DBA]]></category>
		<category><![CDATA[DDL]]></category>
		<category><![CDATA[TSQL]]></category>

		<guid isPermaLink="false">http://sqlserverplanet.com/?p=2246</guid>
		<description><![CDATA[I imagine you are just looking for simple syntax in order to reseed the identity column of a table you just deleted from. Here is the quick version: DBCC CHECKIDENT('##reseed_example', RESEED, @max_seed) And here is an extended example: -- populate a table with identity SELECT ID = IDENTITY(int,1,1) ,name INTO ##reseed_example FROM dbo.sysobjects -- delete [...]]]></description>
		<wfw:commentRss>http://sqlserverplanet.com/tsql/using-dbcc-checkident-to-reseed-a-table-after-delete/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

<!-- Dynamic page generated in 0.514 seconds. -->
<!-- Cached page generated by WP-Super-Cache on 2012-02-04 21:42:31 -->
<!-- Compression = gzip -->
