|
|
|
Old Hand
      
Group: General Forum Members
Last Login: Today @ 3:33 PM
Points: 317,
Visits: 1,368
|
|
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.
Thanks, Ken
|
|
|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: Saturday, June 15, 2013 8:56 AM
Points: 17,
Visits: 516
|
|
HI,
It may be agent SQL Server Agent Job History Log limit is being breached (default is 1000 rows) you can look at msdb..sysjobservers for last run date and time.
HTH - Walter
|
|
|
|
|
SSC-Dedicated
           
Group: General Forum Members
Last Login: Today @ 10:05 PM
Points: 33,112,
Visits: 27,039
|
|
ken.trock (1/9/2013)
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. Thanks, Ken
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.
--Jeff Moden "RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".
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."
For better, quicker answers on T-SQL questions, click on the following... http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following... http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
|
|
|
|
|
Old Hand
      
Group: General Forum Members
Last Login: Today @ 3:33 PM
Points: 317,
Visits: 1,368
|
|
Thanks guys. It looks like having our server support team recycle the SQL Agent service did the trick. All jobs are running through their entire schedules.
Ken
|
|
|
|