DayLight Savings and Sql Agent
Ran a Job yesterday to check how the SQL agent Handles the DayLight Savings
Created the following Table

Table
Created the Following procedure to enter the current Date

Procedure
and Ran the Job every minute from March 28th 2009 22:50 to Mar 29th 2009 3:00 AM
Results:

daylightsaving-results
There was no 01:00 AM on March 29th !!!!. So any jobs scheduled at 01:00 AM will not run. Sql Agent cannot handle it!!!



Nice one GoodMan, Whats the solution to this?
Should we schedule all our jobs to run in the hour of 00:00 or 02:00 or perhaps its irrelevant because it only happens twice a year and we could do something manual.
The thing i find a bit nefarious i that when we change back we could see the hour of 01:00 twice.