This metric returns a count of the job steps that failed in the latest execution of all jobs on the instance. This should be a calculated measure, where the change is what should alert the DBA. If any step in a job fails in the latest execution, this alert counts those failures and returns a […]
One or more SQL Agent jobs exist that are not owned by the database owner. You should fix these jobs so that they’re owned by the appropriate person. If the owning account is removed from Active Directory, the job may fail.
SQL Agent can be configure to notify an operator when a job fails. While failed jobs also surface in the monitoring, proactive notification often allows for a quicker response.
This metric tells you whether a specific SQL Agent job that runs at exactly the same time every day has overrun its expected duration.
This metric returns the longest running instance of the named job in the last hour. By creating multiple custom metrics from this example – one for each job you’re interested in – you can specify alert thresholds for each job individually.
This metric investigates replication jobs, searching for any that may be disabled inappropriately. If any of your replication jobs have been disabled inappropriately, you may not be aware of their state.
This metric investigates backup jobs, searching for any that may be disabled inappropriately. If any of your backup jobs have been disabled inappropriately, you may not be aware of their state.
This metric tracks the amount of data waiting to be sent from the principal database to the mirror. This is known as the send queue.
Mirroring systems can go offline. This metric returns the current state of the mirroring system so you’ll know from a single value what the current status of your mirroring environment is.
This metric allows you to keep track of the role of a given database within your mirroring set up. The single value returned tells you whether the database is the principal or the mirror.