June 8, 2015 at 1:10 pm
SQL 2008 R2 allowed you to schedule a job for a one-time run on the current day.
Why won't SQL 2012?
Don't believe me? Here's my steps on a build 5582 (SP2 + CU5) box. Tell me where I'm going wrong.
1: In SSMS, double-click on an existing SQL Agent job, e.g. "send test email", then click on Schedules.
2: Click New... button and enter "Test run" in the Name textbox.
3: Change the Schedule type dropdown from Recurring to One time. This causes the warning about attempting time travel as per 2008 R2 to be displayed.
4: Change Time value under One-Time occurrence to at least several minutes later than current time. Leave Date value at default (current date).
5: Click OK button to close New Job Schedule dialog box.
6: Note the Yes value in the Enabled column in the Schedule list of the Job Properties window for the current job. Click OK.
7: Double-click the Job Activity Monitor icon in SSMS and note the 'not scheduled' value in the Next Run column for the job.
8: Double-click the job in question in SSMS and click Schedules. Note the No value in the Enabled column. This job will never run.
Is this a bug? Sure feels like one.
Got a workaround?
Cheers
June 8, 2015 at 2:26 pm
First time I've heard of this. Can you try and replicate this with SP2 + CU6?
Cumulative Update package 6 for SQL Server 2012 SP2
Joie Andrew
"Since 1982"
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply