Support for Daylight Savings Time for Trigger Schedules
Setting up the timing of a Trigger, you need to know how far away from UTC you are so you can specify the right time. That value changes for those of us that observe Daylight Savings Time.
The dialog box for setting up a Trigger Schedule should instead have the following three inputs:
1) the LOCAL time you want it to run
2) the Time Zone
3)Adjust for DST.
THAT is the information people have at their disposal.
To adjust for DST, I must EDIT all my Triggers manually to ensure they run at the right hour of the day when we change over to/from DST.
rocket porg commented
Almost shocked that this isn't possible, we don't all live and work in America guys ;-)
Greg Low commented
Agreed. The lack of any way to set a trigger to run at a specific local time is hard to comprehend, and particularly nasty for those that live in areas with DST. Triggers have a timezone field. Why isn't it implemented?
Jeroen H commented
Very much needed! I do want to share one work-around: schedule multiple triggers with future start dates around upcoming daylight savings changes (e.g. we have a trigger schedule to start in October to switch to Winter time, and another in March for Summer, etc.)
Nate Wicke commented
Yes. We really need a feature to adjust the trigger time for DST.
[Deleted User] commented
+1, please add this feature
richard hudson commented
This is very poor. Most legacy systems handle this (SQL Agent) for example. Producing modern technology that introduces bugs that have been fixed 40 years ago should not be something to be proud of or make excuses about...
Tim Kracht commented
Can you please let us know when this feature will be supported officially, as we are approaching production release.
Fang Liu commented