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
Showing posts with label jobs. Show all posts
Showing posts with label jobs. Show all posts
Monday, March 19, 2012
How to catchup job schedule? Scheduled jobs not running.
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
DougI 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 ru
n
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
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
DougI 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 ru
n
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
How to catchup job schedule? Scheduled jobs not running.
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
--
DougI 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
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
--
DougI 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
Sunday, February 19, 2012
How to brute force delete subscriptions ?
Hello,
I restored a huge ReportServer backup on a dev machine and I do not want the subscriptions and their jobs.
I already changed the SMTP server address so emails will go to nowhere.
Now What is the best sequence to get a rid of all subscriptions?
Delete records (or truncate) from the ReportServer.Subscriptions table then delete all the subscriptions jobs or the other way around?
BTY, a centralized management of subscriptions as well as stuffing all these jobs into a folder would be a welcome addition.
Thanks,
Philippe
Safest way would be using a simple script for deleting all subscriptions via DeleteSubscription() SOAP API and rs.exe.|||Igor Taranov -- MSFT wrote:
Safest way would be using a simple script for deleting all subscriptions via DeleteSubscription() SOAP API and rs.exe.
Thank you.
It is going to take me a little time to figure out how to do this.
BOL is not very user friendly about rs.exe.
Philippe
Subscribe to:
Posts (Atom)