InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comTue, 18 Jun 2013 23:22:10 GMT20http://www.sqlservercentral.com/Forums/Topic650924-146-1.aspxFYI, [url=https://connect.microsoft.com/SQLServer/feedback/details/552707/job-disabled-and-schedule-enabled?wa=wsignin1.0#tabs]https://connect.microsoft.com/SQLServer/feedback/details/552707/job-disabled-and-schedule-enabled?wa=wsignin1.0#tabs[/url]Fri, 23 Apr 2010 12:24:46 GMTJon.Morisihttp://www.sqlservercentral.com/Forums/Topic650924-146-1.aspxI guess these are sporadic issues related to job schedules. Is there something we might be missing here?I am getting little confused.Wed, 21 Apr 2010 22:54:58 GMTmohammed moinudheenhttp://www.sqlservercentral.com/Forums/Topic650924-146-1.aspxFew months ago we decided not to have a schedule enabled in disabled jobs to avoid unwanted runs, like described aboveWed, 21 Apr 2010 17:19:07 GMTbarsukhttp://www.sqlservercentral.com/Forums/Topic650924-146-1.aspxNot really. When I used the GUI to enable/disable the jobs, it cleared up the problem. I am pretty sure that the GUI uses the stored proc. You would need to run a trace to be sure.Tue, 20 Apr 2010 14:18:28 GMTLynn Pettishttp://www.sqlservercentral.com/Forums/Topic650924-146-1.aspxSounds like the lesson for the day is to use sp_update_job to enable / disable and to avoid the GUITue, 20 Apr 2010 13:57:43 GMTJon.Morisihttp://www.sqlservercentral.com/Forums/Topic650924-146-1.aspxThe reason I was asking is i had a similar problem when I would failover our mirror databases. The code that was enabling/disabling the database specific jobs wasn't "working". Where the jobs were being disabled, they kept working and where the were being enabled they would run.I had to modify my code to use the sp_update_job stored procedure in the msdb database. Turns out that SQL Server Agent caches the information and this stored procedure forces a notification to SQL Server Agent.Tue, 20 Apr 2010 13:14:17 GMTLynn Pettishttp://www.sqlservercentral.com/Forums/Topic650924-146-1.aspxI just tried to reproduce the issue as well and couldn't do it. This DID occur on my production box this morning though.Tue, 20 Apr 2010 12:47:25 GMTJon.Morisihttp://www.sqlservercentral.com/Forums/Topic650924-146-1.aspxYou can generate the code. Open the job, uncheck the "enabled" button, then "Script to new window"I can't replicate that in 2005. Tried a "regular" job and a maint plan job. Don't recall it ever happening either.You could query these tables for that specific job and see what the enabled values are:sysjobssysjobschedulessysschedulesTue, 20 Apr 2010 11:36:52 GMThomebrew01http://www.sqlservercentral.com/Forums/Topic650924-146-1.aspxGUITue, 20 Apr 2010 10:27:47 GMTJon.Morisihttp://www.sqlservercentral.com/Forums/Topic650924-146-1.aspxAre you disabling the job via the GUI or code? If code, please show the code.Tue, 20 Apr 2010 10:09:38 GMTLynn Pettishttp://www.sqlservercentral.com/Forums/Topic650924-146-1.aspxTry restarting sql server agent service after disabling the job...seems to work for me.Tue, 20 Apr 2010 10:03:16 GMTJon.Morisihttp://www.sqlservercentral.com/Forums/Topic650924-146-1.aspxI'm having the same issue, job disabled, schedule enabled, job runs. (I'm running sql 2008 sp1)My jobs were created via a maintenance plan, were yours too?Tue, 20 Apr 2010 09:42:27 GMTJon.Morisihttp://www.sqlservercentral.com/Forums/Topic650924-146-1.aspxGUI and DB settings are as expected.I have done manual runs atkleast 10 times and same results, Schedule must be Disabled to stop Job.Thu, 05 Feb 2009 12:10:28 GMTphrankboothhttp://www.sqlservercentral.com/Forums/Topic650924-146-1.aspxI've never encountered that. It shows disabled in the GUI ? Does the "Last Run" get updated afterwards ? If you look at the "enabled" field in msdb..sysjobs, what do you see ?Thu, 05 Feb 2009 09:46:28 GMThomebrew01http://www.sqlservercentral.com/Forums/Topic650924-146-1.aspxI'm absolutely sure about it. I ran a Trace on it.Thu, 05 Feb 2009 09:01:10 GMTphrankboothhttp://www.sqlservercentral.com/Forums/Topic650924-146-1.aspx[quote][b]phrankbooth (2/5/2009)[/b][hr]Hello,I can't seem to reconcile this and can't find a clear explanation on it.I have a Job set up with a Recurring schedule.When both Job and its Schedule are Enabled, the Job will run normally.When Job is Enabled but Schedule isn't, the Job will not run.[b]When Job is Disabled but the Schedule is Enabled, the Job runs[/b].I don't get how the Job can be Disabled yet still run when its Schedule is Enabled. What is the purpose then of Enabling a Job is the Schedule is what controls if it runs or not?Thanks![/quote]".. When Job is Disabled but the Schedule is Enabled, the Job runs.."Sounds wrong .... Are you sure about that ??Thu, 05 Feb 2009 08:50:20 GMThomebrew01http://www.sqlservercentral.com/Forums/Topic650924-146-1.aspxHello,I can't seem to reconcile this and can't find a clear explanation on it.I have a Job set up with a Recurring schedule.When both Job and its Schedule are Enabled, the Job will run normally.When Job is Enabled but Schedule isn't, the Job will not run.When Job is Disabled but the Schedule is Enabled, the Job runs.I don't get how the Job can be Disabled yet still run when its Schedule is Enabled. What is the purpose then of Enabling a Job is the Schedule is what controls if it runs or not?Thanks!Thu, 05 Feb 2009 08:24:46 GMTphrankbooth