Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Kristen
Test
22859 Posts |
 Posted - 2006-10-29 : 01:32:53
|
| Should SQL Servers be set to NOT change the clock for DST?When the clocks go back the "start time" of the next scheduled event in the scheduler has not been reached - so hourly tasks don't get executed for 2 hours. We have stuff scheduled for every minute that is not going to run for a whole hour ... hmmmm .... Kristen |
|
|
Michael Valentine Jones
Yak DBA Kernel (pronounced Colonel)
7020 Posts |
Posted - 2006-10-29 : 01:54:39
|
| I usually handle this problem by the simple method of ignoring it.You would probably cause yourself far more problems if you don't change it. Who knows what problems it would cause in your applicaitons?CODO ERGO SUM |
 |
|
|
byrmol
Shed Building SQL Farmer
1591 Posts |
Posted - 2006-10-29 : 02:19:39
|
| >>I usually handle this problem by the simple method of ignoring it.Same here...DST is such a pain in the arse..Take this morning for instance...Better Half: You better go to the dairy and get milk because DST just started.Me: The cows don't care!Better Half: But the milk truck does!DavidMProduction is just another testing cycle |
|
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2006-10-29 : 20:36:51
|
quote:
Should SQL Servers be set to NOT change the clock for DST?
yep, for time requirement we just handle it in the reports instead of changing the actual time to follow DST--------------------keeping it simple... |
|
|
|
|
|
|
Clocks Go Back - Schedules not run?