Data Monitoring / SQL Server Availability & Capacity
SQL Server: Job overrun detection
A scheduled job remains running past the reporting deadline. Compare current elapsed time with comparable historical runs and downstream cutoff requirements.
Environment and inputs: SQL Server operational monitoring; availability groups, SQL Agent and host-level metrics depend on edition, service and deployment.
Failure scenario
A scheduled job remains running past the reporting deadline. Confirm the cause before choosing a fix.
Evidence to collect
Compare current elapsed time with comparable historical runs and downstream cutoff requirements. Record the time, affected scope and a healthy comparison interval.
Fix the confirmed cause
Separate a volume-related long run from a stalled dependency and escalate against the business deadline. Write the expected result first. Change one relevant setting at a time.
Check the result and hand over
Repeat the check for job overrun detection using the same scope and a representative interval. Check that the symptom is resolved, expected records are present and downstream results are correct. If coverage, correctness or latency worsens, restore the recorded configuration through the agreed rollback process.
Scope and precautions
Prefer read-only access and limit queries to the relevant period or dataset. This example has not been tested on your systems. Test changes in an approved environment. Keep credentials and sensitive data out of shared evidence.