|
|
Posted by Erland Sommarskog on 10/01/81 11:19
Mike (mjorlando@campsystems.com) writes:
> Scenario 5 (STILL HAVING THE SAME PROBLEM):
>
> Date: June 20, 2005
> Time: 12:30PM
>
> Deleted schedule 328 from my job and created a new 28-day schedule
> starting tonight 6/20/2005 at 10:00PM.
>...
> The job ran as desired however the next run date was NOT 28 days from
> June 20, 2005 10:00PM. The next run date is June 21, 2005 at 10PM.
> Back to the same problem, but this time I have a before and after row
> in sysjobschedules. After the job ran the row in sysjobschedules looks
> like this:
>...
> I thought I had this problem figured out by creating the schedule after
> noon on the day it was supposed to run. Appearently this job still
> wants to run every day. This is very frustrating since I waited almost
> a month to schedule this job at a specific time so that the schedule
> works on a 28-day interval. What the @##%^#@ is wrong with SQL Server?
> Are there any patches that can be run to fix this?
Well, the first step to find a patch is that the problem can be recreated.
This far I have not been successful. Some 45 minutes ago I created a job
to run every 28th day at 23:15 starting today. The job ran, and is now
scheduled to run 2005-07-19 next time.
But I recalled that your job was a long-running job, so I've now scheduled
a job that will start at 23:45 and run for six hours. We'll see tomorrow
when this will be scheduled to run the next time.
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp
Navigation:
[Reply to this message]
|