InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comThu, 23 May 2013 22:21:50 GMT20http://www.sqlservercentral.com/Forums/Topic1404788-146-1.aspxThanks 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.KenFri, 11 Jan 2013 07:22:05 GMTken.trockhttp://www.sqlservercentral.com/Forums/Topic1404788-146-1.aspx[quote][b]ken.trock (1/9/2013)[/b][hr]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.[code]UPDATE s SET active_end_time = active_end_time + 10000 --Add an hourFROM msdb..sysschedules sINNER JOIN msdb..sysjobschedules js ON js.schedule_id = s.schedule_idINNER JOIN msdb..sysjobs j ON j.job_id = js.job_idWHERE j.name LIKE 'This_Job_Needs_Another_Hour%' AND j.enabled = 1[/code]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[/quote]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.Thu, 10 Jan 2013 07:31:16 GMTJeff Modenhttp://www.sqlservercentral.com/Forums/Topic1404788-146-1.aspxHI,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 - WalterThu, 10 Jan 2013 06:31:00 GMTtelcogodhttp://www.sqlservercentral.com/Forums/Topic1404788-146-1.aspxHas 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.[code]UPDATE s SET active_end_time = active_end_time + 10000 --Add an hourFROM msdb..sysschedules sINNER JOIN msdb..sysjobschedules js ON js.schedule_id = s.schedule_idINNER JOIN msdb..sysjobs j ON j.job_id = js.job_idWHERE j.name LIKE 'This_Job_Needs_Another_Hour%' AND j.enabled = 1[/code]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,KenWed, 09 Jan 2013 07:37:44 GMTken.trock