The SQL Server Agent Jobs page shows SQL Server Agent job status and history for the monitored SQL Server. Use it to review failed jobs, long-running jobs, and maintenance activity.
What You Can Review
- Job names and status.
- Recent outcome.
- Schedule and run history.
- Failed or long-running maintenance tasks.
- Jobs related to backups, index maintenance, integrity checks, or ETL.
Workflow
- Open Agent Jobs.
- Sort by failed, running, duration, or last run time.
- Review job history and message detail.
- Cross-check Error Log for SQL Server messages.
- Use Health Checks for maintenance-related findings.
How To Review SQL Server Agent Jobs
SQL Server Agent job history often explains performance and availability symptoms. Failed backups, long-running index maintenance, ETL jobs, and integrity checks can affect users even when SQL Server itself is online. Use this page to connect scheduled work with alerts, waits, storage growth, and error log messages.
Start with failed jobs and jobs that ran longer than usual. Then compare the job time with SQL Server Activity, SQL Server Waits, SQL Server Files, and SQL Server Error Log. A job that normally runs at night may become visible to users if it overlaps business hours or competes with a new workload.
For operational follow-up, record the job name, run time, duration, outcome, and owner. Recurring job failures should be routed to the team responsible for the job, not just acknowledged in monitoring.
SQL Server Agent FAQ
Why are Agent jobs important for monitoring?
Jobs perform backups, maintenance, imports, exports, and other scheduled work that can affect performance and reliability.
What if SQL Server Agent is not running?
Check service status, SQL Server Error Log, alerts, and whether the instance is expected to use Agent jobs.
Should failed jobs always page someone?
Backup, integrity, and production data movement failures usually need prompt attention. Lower-risk jobs can follow your normal alert policy.