<?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 Performance &#187; Job</title>
	<atom:link href="http://www.sql-server-performance.com/tag/job/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sql-server-performance.com</link>
	<description>SQL Server Performance Tuning</description>
	<lastBuildDate>Mon, 20 May 2013 03:15:15 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
		<item>
		<title>Automatically Retry A SQL Server Job After A Failed Step</title>
		<link>http://www.sql-server-performance.com/2012/automatically-retry-a-sql-server-job-after-a-failed-step/</link>
		<comments>http://www.sql-server-performance.com/2012/automatically-retry-a-sql-server-job-after-a-failed-step/#comments</comments>
		<pubDate>Mon, 19 Nov 2012 02:18:48 +0000</pubDate>
		<dc:creator>Dinesh Asanka</dc:creator>
				<category><![CDATA[Developer]]></category>
		<category><![CDATA[General DBA]]></category>
		<category><![CDATA[Job]]></category>
		<category><![CDATA[sql server agent]]></category>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=3341</guid>
		<description><![CDATA[If you are running SQL Server jobs with numerous steps there can be failures due to network glitches or deadlocks. In such a scenario the DBA will typically restart the job from the failed step. However, there is an option in SQL Server Agent to automatically retry the job, which is under utilized by many [...]]]></description>
		<wfw:commentRss>http://www.sql-server-performance.com/2012/automatically-retry-a-sql-server-job-after-a-failed-step/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SQL Server Agent job syspolicy_purge_history is failing in the cluster environment.</title>
		<link>http://www.sql-server-performance.com/2010/syspolicy-purge-history-failing/</link>
		<comments>http://www.sql-server-performance.com/2010/syspolicy-purge-history-failing/#comments</comments>
		<pubDate>Tue, 12 Oct 2010 01:12:50 +0000</pubDate>
		<dc:creator>Dinesh Asanka</dc:creator>
				<category><![CDATA[General DBA]]></category>
		<category><![CDATA[Agent]]></category>
		<category><![CDATA[Job]]></category>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?=1902</guid>
		<description><![CDATA[When you install or upgrade SQL Server 2008 or R2 you will &#160;see a new SQL Server Agent job named syspolicy_purge_history. In fact this is the only job you will see after installing a brand new SQL Server 2008 instance. This job is relevant to Policy Based Management and by default it has a daily [...]]]></description>
		<wfw:commentRss>http://www.sql-server-performance.com/2010/syspolicy-purge-history-failing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
