﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / Discuss Content Posted by Leo Peysakhovich / Article Discussions / Article Discussions by Author  / Monitoring Failed Job Steps / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Mon, 17 Jun 2013 21:40:28 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: Monitoring Failed Job Steps</title><link>http://www.sqlservercentral.com/Forums/Topic103193-163-1.aspx</link><description>That's an interesting approach.  I've devised a system where i have a table storing job and step id's, recipients, and on_success/on_fail fields and a trigger on sysjobstephistory.  Though both ways are effective, your method seems easier to implement, and slightly less dependant on the system tables.  </description><pubDate>Tue, 01 Mar 2005 10:39:00 GMT</pubDate><dc:creator>spongemagnet</dc:creator></item><item><title>Monitoring Failed Job Steps</title><link>http://www.sqlservercentral.com/Forums/Topic103193-163-1.aspx</link><description>Comments posted to this topic are about the content posted at &lt;A HREF=http://www.sqlservercentral.com/columnists/lPeysakhovich/monitoringfailedjobsteps.asp&gt;http://www.sqlservercentral.com/columnists/l</description><pubDate>Sun, 29 Feb 2004 06:33:00 GMT</pubDate><dc:creator>Leo Peysakhovich</dc:creator></item></channel></rss>