Hi,
I try not to schedule jobs during sw/hw maintenance windows, but sometimes
it happens - even more so now with active windows update running. It just
shuts down without regard to what's running.
Unfortunately, when the sql server comes back up, it doesn't run jobs that
are past due. I can't seem to find any setting that would 'catch-up' the
jobs. Would you share your thoughts on how to deal with this situation.
thanks
Doug
I don't think there is a "built-in" function for this type of situation.
However, you can create your own stored procedure that queries
msdb..sysjobhistory and look for run_status = 0, then use sp_start_job to
start those jobs that failed. And then you can set up a scheduled job to run
this SP during every restart.
"Doug Little" wrote:
> Hi,
> I try not to schedule jobs during sw/hw maintenance windows, but sometimes
> it happens - even more so now with active windows update running. It just
> shuts down without regard to what's running.
> Unfortunately, when the sql server comes back up, it doesn't run jobs that
> are past due. I can't seem to find any setting that would 'catch-up' the
> jobs. Would you share your thoughts on how to deal with this situation.
> thanks
> --
> Doug
No comments:
Post a Comment