Has anyone seen in SQL 2005 SP3 where agent jobs simply don't abide by a schedule setup? I had a bunch of jobs that needed to kickoff an hour longer so I scripted it.
UPDATE s SET active_end_time = active_end_time + 10000 --Add an hour
FROM msdb..sysschedules s
INNER JOIN msdb..sysjobschedules js ON js.schedule_id = s.schedule_id
INNER JOIN msdb..sysjobs j ON j.job_id = js.job_id
WHERE j.name LIKE 'This_Job_Needs_Another_Hour%' AND j.enabled = 1
I made sure a couple look right in the GUI scheduler. They run every 15 minutes and they're definitely not taking longer than that (which would prohibit the job from running on it's next interval). The SQL Agent logs are clear.
The best I can tell is that the agent service should be bounced.
I believe that it's a bit more complicated than that. You have to change the schedule for the job using the built in procs which will also change the "next run time" in the job table, etc, etc.
is pronounced ree-bar and is a Modenism for R
First step towards the paradigm shift of writing Set Based code: Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is not.
Just because you can do something in PowerShell, doesnt mean you should. Helpful Links:
How to post code problemsHow to post performance problemsForum FAQs