SQL 2005 Job Scheduling Bug?

[Catadmin]

Has anyone else noticed this?

I've got a job scheduled to run Weekly -> Every 4 weeks on Thursday from January 4th - February 1st. To me, that translates to run it on January 4th and either January 2th or February 1st (depending of if SQL Server counts the first time it ran in the 4 weeks difference or not) and that's it.

But this morning, the job ran as if it were scheduled every 1 week. I've double-checked the job properties and it is set correctly. I don't want it set Monthly because my schedule doesn't quite follow the Monthly thing. I can't set it Daily...

Thoughts?



Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"

 

[ptheriault]

I know this might be stupid question but what does the description say?

Does is say something like.

Occurs every 4 week(s) in Monday at some time. Schedule will be used starting on some Date.

- Paul
- If at first you don't succeed, find out if the loser gets anything.

 

[Catadmin]

The only stupid question is the one that was never asked. @=)

Occurs every 4 week(s) on Thursday at 5:00:00 AM. Schedule will be used between 1/4/2007 and 2/1/2007.

That tells me that every four weeks it'll happen. Not every week.



Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"

 

[mrdenny]

Did the job run on the 4th?

Denny
MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005) / MCITP Database Administrator (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[Catadmin]

The history says it did, but the fact that you ask me reminds me of another problem we had with a DBA not enabling the schedules he created.

I'm thinking the job might have manually been run and the schedule was probably enabled after the last run. Which would explain why the job ran this morning when it shouldn't have.

I'm going to watch it for another week and see.





Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"

 

[Catadmin]

DOH!

It looks like the guy who set it up set it up after the time it was supposed to run. As in 1/4/07 post-5 a.m. is when the job schedule was created.

No wonder it fired off today. <shakes head>



Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"

 

[ptheriault]

If it was manually run the history should tell you who executed the job.

- Paul
- If at first you don't succeed, find out if the loser gets anything.