August 27, 2002 at 8:52 pm
I have a development server and I have to change the date to about a month in the future once a quarter so the users can test their time sensitive application. The jobs in SQL Agent get left with the next start date set based on the old date and never start again. My steps are:
1) Stop SQL Server
2) Reset system time
3) Re-start SQL Server
4) Re-start Agent
Any ideas how to force Agent to re-calculate the next run date for the jobs?
August 28, 2002 at 4:05 am
I am confused by what you are doing. However, try this.
Reset the system time, 7 syncs within a few seconds and 2000 seems instantaneous.
Next use sp_update_jobschedule to disable the jobs then reenable the jobs, this should force a reset as to next run.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
August 28, 2002 at 5:01 am
Or just update sysjobs directly. Or maybe backup msdb prior to the test, then restore afterwards?
Andy
August 28, 2002 at 7:22 am
Take a look at the system stored procedure sp_update_jobschedule. We use it to reschedule a job every 15 minutes if a mainframe extract hasn't transferred yet.
K. Brian Kelley
http://www.truthsolutions.com/
Author: Start to Finish Guide to SQL Server Performance Monitoring
http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1
K. Brian Kelley
@kbriankelley
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply