SQL 2012 Agent Job Yearly Scheduling Bug

SQL 2012 Agent Job Yearly Scheduling Bug by addamse

Closed

Type:	Bug
ID:	775811
Opened:	1/4/2013 8:52:25 AM
Access Restriction:	Public

Workaround(s)

view

User(s) can reproduce this bug

I scheduled a SQL Agent job to run once in 12 months and surprisingly the job is executing monthly. Here is my job schedule definition:
Occurs every 12 month(s) on day 3 of that month at 3:00:00 AM. Schedule will be used starting on 1/3/2012.

It is the same issue as the below connect post (which is for SQL 2008 R2) but I am using SQL 2012 CU4. Has this fix not yet been made in SQL 2012?
https://connect.microsoft.com/SQLServer/feedback/details/722235/sql-agent-job-yearly-scheduling

Details (expand)

English

SQL Server 2012 - Standard Edition

Tools (SSMS, Agent, Profiler, Migration, etc.)

Windows Server 2008 R2 Standard (SP1)

English

Schedule a job to run once in 12 months.

Occurs every 12 month(s) on day 3 of that month at 3:00:00 AM. Schedule will be used starting on 1/3/2012.

The next schedule date is for 2/3/2013 at 3 AM. Job executes every month.

Should be running on yearly schedule not monthly.

X64

Other (e.g. VM Ware, specify in Description)

0 attachments

Posted by addamse on 5/7/2013 at 6:55 AM

I am still able to re-produce this issue. I am on SQL 2012 Standard CU5 now and still see the issue. Steps to re-produce:
- Create a new job
- Create the job schedule as "Occurs every 12 month(s) on day 3 of that month at 3:00:00 AM. Schedule will be used starting on 1/3/2013."
- Save the job
- Run the following query:
USE msdb
GO
SELECT *
FROM sysjobschedules A
inner join sysjobs b ON A.job_id = B.job_id
where B.name = 'TestJobName'

- See the next_run_date column value: The values is: "20130603". Which is incorrect, it should be "20140103".

Posted by Microsoft on 5/6/2013 at 10:29 AM

Hello, we were not able to repro this issue. Please refer to our blog post about scheduler issues that we fixed: http://blogs.msdn.com/b/sqlagent/archive/2012/03/14/sql-agent-scheduler-issues.aspx
and make sure that you have correct version. We will go ahead and close this issue as Not Repro, you can always reactivate it and provide more details.

Thank you
Alex Grach [MSFT]

Posted by Microsoft on 3/5/2013 at 8:26 AM

Thanks for reporting this issue. We are investigating this issue. We shall keep you posted soon with our findings