October 18, 2016 at 12:08 am
Comments posted to this topic are about the item Which Time Zone?
October 18, 2016 at 1:10 am
Sorry didn't like that one Steve, totally unfamiliar with the AT TIME ZONE command, and of course I got it wrong.
Doh!
October 18, 2016 at 2:23 am
BillLudlow (10/18/2016)
Sorry didn't like that one Steve, totally unfamiliar with the AT TIME ZONE command, and of course I got it wrong.Doh!
Not knowing what Mountain Time was didn't help either :hehe:
October 18, 2016 at 4:30 am
I would say that's a little ambiguous of a question. You don't state whether the time in the question is your local time, or the UTC time, which would result in differing answers.
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
October 18, 2016 at 8:54 am
Thom A (10/18/2016)
I would say that's a little ambiguous of a question. You don't state whether the time in the question is your local time, or the UTC time, which would result in differing answers.
Well, since I said I executed the batch at a certain time, in my time zone, I'd assume that you'd take this as executed at UTC -6 on this date.
October 18, 2016 at 9:44 am
I got it wrong, too, but it was my haste. Thanks for the question, Steve!
October 18, 2016 at 10:37 am
sneaky, sneaky Steve. Thank you for exposing this new feature... :blink:
October 21, 2016 at 6:36 pm
BillLudlow (10/18/2016)
Sorry didn't like that one Steve, totally unfamiliar with the AT TIME ZONE command, and of course I got it wrong.Doh!
Me too. I thought SQL Server would assume the the time it was given was in the time zone in which it was running if the input didn't include an offset, so would have got it wrong, and then accidentally selected a different wrong answer from the one I meant to select. Must request SWMBO not to shout for help over trivia when I'm trying to type or click.
So for me it's a good question, because I've learnt something new about AT TIME OFFSET
Incidentally, MS (or at least SQL Server) apparently still thinks Portugal, Canary Islands, Faroe Islands, UK, Western Sahara, and Morocco are all currently using UTC+0200, when we're actually all on UTC+0100, because it's invented an imaginary "Western European Standard Time" zone which is UTC+0100in winter and UTC+0200 in the summer, and all the places named use WEST (Western European Summer Time, UTC+0100) in the summer and WET (Western European Time, UTC+0000) in the winter. There is no such zone as Western European Standard Time (unless that name is used to refer to Western European Time, which is not what the SQL Server imaginary zone name does), the S in WEST stands for SUMMER.
Tom
October 21, 2016 at 7:26 pm
TomThomson (10/21/2016)
BillLudlow (10/18/2016)
Sorry didn't like that one Steve, totally unfamiliar with the AT TIME ZONE command, and of course I got it wrong.Doh!
Me too. I thought SQL Server would assume the the time it was given was in the time zone in which it was running if the input didn't include an offset, so would have got it wrong, and then accidentally selected a different wrong answer from the one I meant to select. Must request SWMBO not to shout for help over trivia when I'm trying to type or click.
So for me it's a good question, because I've learnt something new about AT TIME OFFSET
Incidentally, MS (or at least SQL Server) apparently still thinks Portugal, Canary Islands, Faroe Islands, UK, Western Sahara, and Morocco are all currently using UTC+0200, when we're actually all on UTC+0100, because it's invented an imaginary "Western European Standard Time" zone which is UTC+0100in winter and UTC+0200 in the summer, and all the places named use WEST (Western European Summer Time, UTC+0100) in the summer and WET (Western European Time, UTC+0000) in the winter. There is no such zone as Western European Standard Time (unless that name is used to refer to Western European Time, which is not what the SQL Server imaginary zone name does), the S in WEST stands for SUMMER.
UTC + 0100 at one time of year and UTC + 0200 at another time? That sounds like a fabulous idea...what could possibly go wrong? :hehe:
October 21, 2016 at 9:59 pm
Ed Wagner (10/21/2016)
TomThomson (10/21/2016)
BillLudlow (10/18/2016)
Sorry didn't like that one Steve, totally unfamiliar with the AT TIME ZONE command, and of course I got it wrong.Doh!
Me too. I thought SQL Server would assume the the time it was given was in the time zone in which it was running if the input didn't include an offset, so would have got it wrong, and then accidentally selected a different wrong answer from the one I meant to select. Must request SWMBO not to shout for help over trivia when I'm trying to type or click.
So for me it's a good question, because I've learnt something new about AT TIME OFFSET
Incidentally, MS (or at least SQL Server) apparently still thinks Portugal, Canary Islands, Faroe Islands, UK, Western Sahara, and Morocco are all currently using UTC+0200, when we're actually all on UTC+0100, because it's invented an imaginary "Western European Standard Time" zone which is UTC+0100in winter and UTC+0200 in the summer, and all the places named use WEST (Western European Summer Time, UTC+0100) in the summer and WET (Western European Time, UTC+0000) in the winter. There is no such zone as Western European Standard Time (unless that name is used to refer to Western European Time, which is not what the SQL Server imaginary zone name does), the S in WEST stands for SUMMER.
UTC + 0100 at one time of year and UTC + 0200 at another time? That sounds like a fabulous idea...what could possibly go wrong? :hehe:
I wouldn't expect anything to go wrong if they said that zone was Central European Time (which fits France, Belgium, Netherlands, Germany, Denmark, Switzerland, Austria, Spain except Canaries, Italy, and so on. But they say it's Western European Standard Time, which is nonsense. Oddly MS have both Central Europe Time and Central Europe Standard Time while the rest of the world recognise Central European Time (zone) and Central European Summer Time (used by some coutries in CET zone when it's summer).
Tom
October 25, 2016 at 2:46 am
Ugh. I hate time zones 😀
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
October 25, 2016 at 6:13 am
Koen Verbeeck (10/25/2016)
Ugh. I hate time zones 😀
I don't actually hate time zones, but I do hate MS's hopelessly misleading names for some of them.
Tom
October 25, 2016 at 7:09 am
TomThomson (10/25/2016)
Koen Verbeeck (10/25/2016)
Ugh. I hate time zones 😀I don't actually hate time zones, but I do hate MS's hopelessly misleading names for some of them.
I don't like the inconsistent implementation of them around the world. It seems like there are more special cases, one-offs and stupid decisions that were made just to be different. I get that it's up to each government how to run their country. It just makes life unnecessarily complicated when trying to conduct business that's sensitive to the time of day.
Viewing 13 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply