April 5, 2012 at 10:04 am
Nice question Steve, learned something new today.
April 5, 2012 at 2:30 pm
mtassin (4/5/2012)
Thanks for an easy one.I personally love this data type... it makes dealing with multi-time zone data a little bit easier.... datetime data still gives me more headaches than any other.
"Ok Ms. Smith we'll schedule a callback at 3pm your time in California on Friday"
Ok so she's in a portion of California that doens't follow DST, we're in Chicago and we do.
Is Friday in or out of DST? Do we know her correct TZ? What about when our east coast support team decides to handle this one?
*sigh*
Headaches I tell you... 🙂
+1 on that. I wish I'd had this data type and this function years back. We had customers in 4 time zones raging from +05:30 to -06:00.
Tom
April 6, 2012 at 7:46 am
Something seems contradictory in the answer to this question. First it says the answer is 2012/04/05 11:00:00 +05:00. Then in the explanation it says the GMT time of the result is 2012/04/05 11:00 (in other words, the answer is 2012/04/05 11:00 +00.00).
Well those two times are 5 hours apart, so they both can't be right.
April 8, 2012 at 11:23 am
Good straightforward question. Thanks for submitting.
http://brittcluff.blogspot.com/
April 9, 2012 at 8:31 am
Good question. Never used this data type before but I have a project coming my way soon where I may be able to leverage datetimeoffset. Very "timely" har har. Thanks.
Chris Umbaugh
Data Warehouse / Business Intelligence Consultant
twitter @ToledoSQL
April 11, 2012 at 8:24 am
Thank you for the learning opportunity with the topic.
October 9, 2012 at 1:40 am
nice question..
learn something new today!!:-)
_______________________________________________________________
To get quick answer follow this link:
http://www.sqlservercentral.com/articles/Best+Practices/61537/
January 9, 2013 at 6:36 am
Nice one..
--
Dineshbabu
Desire to learn new things..
Viewing 8 posts - 16 through 22 (of 22 total)
You must be logged in to reply to this topic. Login to reply