SQL 2012 Agent Job Yearly Scheduling Bug - by addamse

Status : 

  Duplicate<br /><br />
		This item appears to be a duplicate of another existing Connect or internal item.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


1
0
Sign in
to vote
ID 775811 Comments
Status Closed Workarounds
Type Bug Repros 2
Opened 1/4/2013 8:52:25 AM
Access Restriction Public

Description

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



Sign in to post a comment.
Posted by Microsoft on 10/11/2013 at 9:22 AM
Hello Addamse.
This issue is already being tracked in another work item. As such, this will be closed as a duplicate. Please see below for updates.
http://connect.microsoft.com/SQLServer/feedback/details/801203/sql-server-2008-yearly-agent-jobs-run-monthly
-Walter A Jokiel, Program Manager, SQL Server (wajokiel@microsoft.com)
Posted by addamse on 10/11/2013 at 5:11 AM
Yesterday this was marked as "Resolved as Duplicate". Can you please point me to the connect item where this issue was addresses so I know how to fix it? Thanks.
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