Hi All,

I got a problem with our SQL agent jobs due to DST time change, and hope you 
can shed some light on what might have happened. We are running SQL 2005 SP2 
CU9 64bit EE on Win 2k3 64bit EE.

The problem: We have about 10 log backup jobs for manual log shipping 
purposes. Jobs are schedule to run hourly on 10th minute of every hour 
(1:10am, 2:10am etc.).  But for some reason, when DST time change happened, 
all jobs ran at 3:02am which was totally unexpected, and then all ran again 
at 3:10am. Due to the file naming convention we are using, the later run 
actually overwrote the files backed up at prior run causing the log shipping 
to fail.

My question is, how and why the jobs ran at 3:02am? they are not scheduled 
even close to the time.

Any help/idea is much appreciated.

-- 
Brian

After the 1:10 job ran, the next scheduled run was at 2:10am.  But at
2:00am, the time changed to 3:00am.  At that point, the job that was
scheduled at 2:10am was triggered because the time elapsed past 2:10am
trigger point.  The next scheduled run was at 3:10am, so that job ran
on the normal schedule at 3:10am and your naming convention overwrote
the file.

-Eric Isaacs