As many of you know, Daylight Savings Time (DST) in the United States is changing this year to start on March 11th, 2007 (3 weeks earlier than normal) and end on November 4th, 2007 (1 week later than normal). I thought I would write a quick post on the impact of these changes on SQL Server.
The impact can be summarized in 3 key points:
- Notification Services is the ONLY SQL product that has a DST 2007 bug and requires a fix to be applied. You can find this update at the following KB article http://support.microsoft.com/kb/931815
- SQL Server Engine, Analysis Services, etc. uses/relies on Windows for many date/time functionalities, so if you have the proper updates for Windows there should be no noticeable issues. You can find the proper updates for Windows at this KB article http://support.microsoft.com/kb/931836
- There are other perceived DST issues for SQL Server that have been around that are not specific to the 2007 change but you may perceive them to be related. You can read about these issues at this KB article http://support.microsoft.com/kb/931975
Microsoft has created a web page to guide customers on any updates or issues they should take action on for the upcoming DST changes. You can find this web page at http://support.microsoft.com/gp/dst_overview.
Please take the time to review these article and web resources. Don't wait until March 10th to check on what updates or issues may affect your computers and/or software.
Bob Ward, Microsoft