https://www.sqlserver70.com/tags/job-monitoring/Recent content in Job Monitoring on SQL Server ScriptsHugo -- gohugo.ioenSQLServer70.comSat, 11 Apr 2026 00:00:00 +0000https://www.sqlserver70.com/post/sql-server-agent-job-failure-history-report/Sat, 11 Apr 2026 00:00:00 +0000https://www.sqlserver70.com/post/sql-server-agent-job-failure-history-report/ <h2 id="report-sql-server-agent-job-status-and-failure-history">Report SQL Server Agent Job Status and Failure History</h2> <p>This script queries the SQL Server Agent job history stored in msdb to produce a detailed report of each job's most recent run status, failure and success counts over the last 60 days, total lifetime run counts, and job step information including subsystem type and proxy name.</p> <script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-1012089347386563" crossorigin="anonymous"></script> <ins class="adsbygoogle" style="display:inline-block;width:728px;height:90px" data-ad-client="ca-pub-1012089347386563" data-ad-slot="8593449130"></ins> <script> (adsbygoogle = window.adsbygoogle || []).push({}); </script> <h2 id="purpose-and-overview">Purpose and Overview</h2> <p>SQL Server Agent jobs automate the critical work of database backups, index maintenance, integrity checks, ETL loads, and more. When a job fails, the impact can range from a missed backup to a halted data pipeline. Knowing which jobs failed, how recently they failed, and whether failures are isolated events or a recurring pattern is essential for any DBA. This script, written by Jason Brimhall and published in the ktaranov/sqlserver-kit community repository, uses a series of common table expressions to build a rich job history report. It shows the most recent outcome for each job status type, counts failures and successes within the last 60 days relative to the latest run, and includes job step details. To report only failures, uncomment one line. Run this script in the context of the <code>msdb</code> database.</p>