Prev: Security Update KB970895 for SLQ Server 2005 SP2 fails to install
Next: SQL 2008 - What happened to the "Show ... Pane"
From: Samuel on 1 Apr 2010 20:36
Hi,
I recently created a SQL Server (2008) job "X" and scheduled to run everyday
10:00 AM. The following week I created another SQL Server job "Y" by
scripting out job "X" and scheduled it to run one time only on Friday 11:00
PM.

On Monday I happened to look at the Job Activity monitor and was suprised to
see the job "X" had not run on Saturday and "Sunday". Thinking that someone
had changed the scheduled of job "X", I changed the schedule to everyday
10:00 AM. Again to my suprise saw the next day the job "Y"'s scheduled was
changed to everyday 10:00 AM.

From the sysschedule tables identified that the both the jobs where using
same schedule_id and schedule_uid.

Looks like there is an issue/bug with scripting jobs and creating them on
the same server. It is obvious that the scripted text had schedule_id and
schedule_uid that of the scripted job.

Shibu Samuel
 | 
Pages: 1
Prev: Security Update KB970895 for SLQ Server 2005 SP2 fails to install
Next: SQL 2008 - What happened to the "Show ... Pane"