March 17, 2005 at 7:34 am
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
March 17, 2005 at 7:56 am
If I need a daily task (or whatever time period), and I need to take into account server reboots unannounced, then I tend do write my own scheduler (using Perl). On invocation (which is every 5 mins or so), it checks the last run date in a status file which is written to disk after each successful run.
If it's not run for this time period, it then carries on merrily performing the task you want done.
You can script in your own time windows of opportunity, and times to avoid quite easily.
A five minutely invocation is usually enough resolution to make sure something gets done sharpish (you can make it every 15 mins or whatever resolution you think is best), and the overhead of starting up a small Perl process is pretty much negligible.
March 18, 2005 at 3:20 am
In general I just keep a timewindow open for automatic update. But I once used a batch file that started on windows startup. It used head to read the first line of the logfile to check the date and if that was not the same as %date% the batchfile whould start isql . Not as elegant as Rich's method, but it also worked.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply