What’s the issue?
SQL Server Agent is the scheduling and automation service that runs alongside the SQL Server database engine. It is responsible for executing scheduled jobs (backups, integrity checks, index maintenance, ETL processes), responding to alerts, and sending notifications to operators. This finding indicates that the SQL Server Agent service is currently stopped or disabled on an instance where it should be running.Why is this a problem?
When SQL Server Agent is offline, every scheduled job stops running. This commonly means backups are not being taken, integrity checks are not running, indexes are not being maintained, and ETL or business processes that depend on SQL Agent are silently failing. Alerts for critical errors such as severity 19 through 25 or I/O errors 823, 824, and 825 will not fire, removing your early warning system for corruption and hardware problems.Because Agent failures often go unnoticed until someone needs a backup or notices stale data, the impact may not become apparent until a crisis occurs and recovery options have already been compromised.
What should you do about this?
Start the SQL Server Agent service immediately through Services.msc, SQL Server Configuration Manager, or by running net start SQLSERVERAGENT (adjust the service name for named instances). Set the service startup type to Automatic so it starts with the operating system, and confirm the service account has the permissions it needs. Review the SQL Server Agent error log and the Windows event log to determine why the service was stopped, since causes range from manual intervention to permission problems, failed dependencies, or service account password expiration.Once Agent is running again, verify that recent jobs have executed successfully and investigate any that were missed during the outage, particularly backups and integrity checks.