New DST legislation in West Australia
-
After some careful consideration by our political masters, WA will be trialling this 'new fangled' DST concept as of December 3rd this year, so I've only got a few days left to prepare for the clocks going forward 1 hour this Sunday morning.
While Oracle doesn't do anything crude with time values but uses it's own method of stamping time, please could someone describe how MS SQL stores time values and indicate if it's something one needs to worry about. i.e. does it store time data in what is essentially the sysdate from the OS or does it use a similar techniques to Oracle?!
I appreciate the clocks going forward would be unlikely to cause a problem,
but any advice on what to look for when they go back in a few months would be particularly welcomed.
Thanks in advance
-
I've never encountered any problems with time travel on sql server, here in the UK we have our sleep patterns interrupted twice yearly.
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/ -
SQL Server gets time from the OS, which gets it from the hardware clock. An update, like the DST we have in the US, is slightly delayed (a second or so) from the OS change, but it's updated automatically.
Follow me on Twitter: http://www.twitter.com/way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com -
Thanks fella's, so basically it's a case of sitting back and letting the quickly thrown together patch (as we're new entrants to DST) do it's thang and SQL server will catch up. Sweet.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply