<?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 &#187; DBA</title>
	<atom:link href="http://sqlserverplanet.com/category/dba/feed" rel="self" type="application/rss+xml" />
	<link>http://sqlserverplanet.com</link>
	<description>Tips and Articles on SQL Server</description>
	<lastBuildDate>Thu, 03 May 2012 23:47:51 +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>Increase Job History</title>
		<link>http://sqlserverplanet.com/dba/increase-job-history</link>
		<comments>http://sqlserverplanet.com/dba/increase-job-history#comments</comments>
		<pubDate>Mon, 09 Apr 2012 04:35:43 +0000</pubDate>
		<dc:creator>Derek Dieter</dc:creator>
				<category><![CDATA[DBA]]></category>

		<guid isPermaLink="false">http://sqlserverplanet.com/?p=2359</guid>
		<description><![CDATA[The SQL Server Agent by default only keeps 1000 rows of history for all jobs. There is also a limitation for each job to keep only 100 rows each. These rows do not only include the a row for the entire job, but the rows for each step in the job also. These rows can [...]]]></description>
		<wfw:commentRss>http://sqlserverplanet.com/dba/increase-job-history/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Using DBCC INPUTBUFFER</title>
		<link>http://sqlserverplanet.com/troubleshooting/using-dbcc-inputbuffer</link>
		<comments>http://sqlserverplanet.com/troubleshooting/using-dbcc-inputbuffer#comments</comments>
		<pubDate>Mon, 09 Apr 2012 04:03:54 +0000</pubDate>
		<dc:creator>Derek Dieter</dc:creator>
				<category><![CDATA[DBA]]></category>
		<category><![CDATA[Troubleshooting]]></category>
		<category><![CDATA[DBCC INPUTBUFFER]]></category>
		<category><![CDATA[sp_who3]]></category>

		<guid isPermaLink="false">http://sqlserverplanet.com/?p=2231</guid>
		<description><![CDATA[This command shows the last statement executed for a particular SPID. This statement is mostly used for troubleshooting purposes to determine the exact command a particular SPID is running. You must be a member of the sys admin fixed server role, or have VIEW SERVER STATE permission (if SQL 2005+). As for a real world [...]]]></description>
		<wfw:commentRss>http://sqlserverplanet.com/troubleshooting/using-dbcc-inputbuffer/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Making a Procedure Available in all Databases</title>
		<link>http://sqlserverplanet.com/design/making-a-procedure-available-in-all-databases</link>
		<comments>http://sqlserverplanet.com/design/making-a-procedure-available-in-all-databases#comments</comments>
		<pubDate>Thu, 29 Mar 2012 05:05:44 +0000</pubDate>
		<dc:creator>Derek Dieter</dc:creator>
				<category><![CDATA[DBA]]></category>
		<category><![CDATA[Design]]></category>

		<guid isPermaLink="false">http://sqlserverplanet.com/?p=2333</guid>
		<description><![CDATA[If you&#8217;ve ever wondered how to make a procedure available in any database, it&#8217;s actually pretty simple. If you create a procedure in the master database with the prefix of &#8220;sp_&#8221;, it will be callable from any database. I personally think this feature is great for utilities, however I would not use this for dependent [...]]]></description>
		<wfw:commentRss>http://sqlserverplanet.com/design/making-a-procedure-available-in-all-databases/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Find Triggers and Associated Tables</title>
		<link>http://sqlserverplanet.com/scripts/find-triggers-and-associated-tables</link>
		<comments>http://sqlserverplanet.com/scripts/find-triggers-and-associated-tables#comments</comments>
		<pubDate>Thu, 29 Mar 2012 04:15:07 +0000</pubDate>
		<dc:creator>Derek Dieter</dc:creator>
				<category><![CDATA[DBA]]></category>
		<category><![CDATA[Scripts]]></category>

		<guid isPermaLink="false">http://sqlserverplanet.com/?p=2331</guid>
		<description><![CDATA[These simple snippets of code will show all triggers in the current database, along with the tables they belong to. Unfortunately the INFORMATION_SCHEMA views do not show triggers so we need to revert to using less documented options. The proper way would be to use the INFORMATION_SCHEMA.TRIGGERS view, however SQL Server has yet to create [...]]]></description>
		<wfw:commentRss>http://sqlserverplanet.com/scripts/find-triggers-and-associated-tables/feed</wfw:commentRss>
		<slash:comments>0</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>

