SQL Server Job scheduler 2000 SP2 malfunction? | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

SQL Server Job scheduler 2000 SP2 malfunction?

SQL Server Agent Job scheduler on SQL Server 2000 SP2 malfunction ? I have created a sql job on a SQL Server 2000 which I wanted to schedule to run at the beginning of each year on 1-st January a few minutes after midnight. Because the scheduler only allows to schedule jobs daily, weekly or monthly, I selected "monthly" and then I’ve set it up to occur on day 1 of every 12 months at hour 12:04:00 starting with day 01/01/2006.
After applying the settings, the schedule description read "Occurs every 12 month(s) on day 1 of that month, at 12:04:00 AM". Everything seemed to work fine. On the date 01/01/2006 it automatically launched itself and after successful completion the "Next Run Date" field turned into "01/01/2007 12:04:00".
Surprisingly, the job had executed on "1-st Ferbruary 2006 at 12:00:00" as well automatically without anybody modifying the initial job schedule. On a different server the same sql job with the exact same schedule set up had executed once more on "1-st of May 2006 at 12:00:00".
Why this behaviour? They were supposed to run once each year but only on 1-st of January. Can anybody give me a few ideas ? What actions might have caused this ? Could this happen after a machine reboot ? Could this be a result of windows updates ? Is this a known issue of MS SQL Server Agent 2000 scheduler on SQL Server SP 2 ? I want to mention that the machines where this malfunction occured have SQL Server 2000 SP2 installed.
Thanks.
Test and apply SQL server service pack 4 in this case. Satya SKJ
Microsoft SQL Server MVP
Contributing Editor & Forums Moderator
http://www.SQL-Server-Performance.Com
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
Thank you for the quick reply, Satya. My problem is that by executing, the sql job has altered some data in our database.
I would like to know if this behaviour is a known issue with SP 2 so I can justify somehow the data loss. Is there a list with all shortcomings of sql sp2 ?
quote:Originally posted by satya Test and apply SQL server service pack 4 in this case. Satya SKJ
Microsoft SQL Server MVP
Contributing Editor & Forums Moderator
http://www.SQL-Server-Performance.Com
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.

I can’t find anything about your problem. Try to install sp4 in test server and test it. Luis Martin
Moderator
SQL-Server-Performance.com Although nature commences with reason and ends in experience it is necessary for us to do the opposite, that is to commence with experience and from this to proceed to investigate the reason.
Leonardo Da Vinci Nunca esperes el reconocimiento de tus hijos, eso ocurrirá luego de tu muerte
All postings are provided “AS IS” with no warranties for accuracy.
There may be lot of bugs fixed as compared to SP2 & SP3a, so SP4 has also got more to compare.
I’m not sure or remember what kind of issues fixed in SP2 but it is ideal to get the latest service pack tested & applied. Satya SKJ
Microsoft SQL Server MVP
Contributing Editor & Forums Moderator
http://www.SQL-Server-Performance.Com
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
Apply SP4. Probably next time, you might want to test any new job first before relying on it <img src=’/community/emoticons/emotion-1.gif’ alt=’:)‘ />.<br /><br />May the Almighty God bless us all!<br />www.empoweredinformation.com
]]>