SQL Server 2008 - Yearly Agent Jobs Run Monthly - by ling_0314

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 801203 Comments
Status Closed Workarounds
Type Bug Repros 2
Opened 9/17/2013 11:36:34 AM
Access Restriction Public


I have found 3 separate postings reporting this bug for different versions of SQL Server, from 2005 to 2012. The answers to these posting suggest the the fix has already been put in with SQL Server 2008 Service Pack 2. We are currently using 2008 woth Service Pack 2 but we still have this problem. We have two separate jobs that are supposed to run on a specified date once a year. But both have been run on the same day of the following months. One of the jobs is to insert data for the new year and has caused and will continue to cause havoc if we allow the problem to continue because of the incorrect date when the job was run. 

The version we are currently using is: Microsoft SQL Server 2008 R2 (SP2) - 10.50.4000.0 (X64) 
Sign in to post a comment.
Posted by Microsoft on 10/3/2013 at 11:45 AM
Hello Ling.
Thank you for bringing this to our attention. We really do appreciate the feedback. We’ll investigate and get back to you.
-Walter A Jokiel, Program Manager, SQL Server (wajokiel@microsoft.com)
Posted by .Dariusz.K on 10/2/2013 at 7:08 AM
I have had a similar problem with the same SQL edition. Microsoft SQL Server 2008 R2 (SP2) - 10.50.4270.0 (X64)

I was able to reproduce it by disablinng and re-enabling the schedule.