December 6, 2011 at 9:00 pm
Comments posted to this topic are about the item DATETIME 1
December 6, 2011 at 10:16 pm
great question (if you didnt run the t-sql)....certainly whipped by butt today 🙂
lesson learned.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This thing is addressing problems that dont exist. Its solution-ism at its worst. We are dumbing down machines that are inherently superior. - Gilfoyle
December 6, 2011 at 10:21 pm
bitbucket, you are thereby appointed an SQLServerCentral sneak in residence. 🙂
Thanks for an interesting QotD!
December 6, 2011 at 10:30 pm
Revenant (12/6/2011)
bitbucket, you are thereby appointed an SQLServerCentral sneak in residence. 🙂Thanks for an interesting QotD!
Why thank you for the compliment. And when you try my next QOD scheduled for publication 14 Dec 2011 - why you might even want to repeat that appointment or give me another one such as
"Chief SQLServerCentral sneak in residence."
Oh a question for you ... should I add that title to my signature block?
December 7, 2011 at 12:14 am
Great question, but the answer is language dependant since outside the us at first glance '01-08-2011' reads 1st of August 😉
December 7, 2011 at 12:31 am
Good question. At first glance I had a hunch there was something sneaky about it.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
December 7, 2011 at 1:10 am
Thank you for the question
Iulian
December 7, 2011 at 1:47 am
ma-516002 (12/7/2011)
Great question, but the answer is language dependant since outside the us at first glance '01-08-2011' reads 1st of August 😉
Fully agree--thus I'd always be in favor of ISO 8601 notation of YYYY-MM-DD (2010-01-08, aka international date) when writing dates without the month's name in it.
Thanks for a good and easy question :-).
December 7, 2011 at 2:21 am
First I got 53,30,1,32 - but soon realised you're using an ambiguous date format.
Thanks for the question:
Week 53 is quite a common occurrance where I work, so it came as no surprise that SQL Server has started implementing it. I may simplify some of our procedures that calculate week 53 if this iso_week function fits our requirements.
December 7, 2011 at 2:28 am
Nice question, learned about iso_week.
It would have been better if the dates were in ISO format, but that's just a detail.
You could derive the answer immediately if you just found the week for the 1st of January of 2010, so it isn't even necessary to look at the rest of the question 🙂
edit: and there were certainly no problems with the font size of the question 😀
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
December 7, 2011 at 4:51 am
<sigh>
When will people finally learn that the US date format is NOT universal??
For a large majority of the world, the correct answer is 53, 31, 1, 32.
December 7, 2011 at 5:38 am
Hugo Kornelis (12/7/2011)
<sigh>When will people finally learn that the US date format is NOT universal??
For a large majority of the world, the correct answer is 53, 31, 1, 32.
And there are many of us in the US that wish we used the same system as most others - just makes more sense. Now, about the metric system .....
Also, BitBucket, thanks for the question. I was weak on iso_week, but no longer thanks to you!
[font="Verdana"]Please don't go. The drones need you. They look up to you.[/font]
Connect to me on LinkedIn
December 7, 2011 at 5:54 am
Learned something new today. Thanks for the great question.
http://brittcluff.blogspot.com/
December 7, 2011 at 8:05 am
nice question!!!
thanks!
December 7, 2011 at 8:12 am
ma-516002 (12/7/2011)
Great question, but the answer is language dependant since outside the us at first glance '01-08-2011' reads 1st of August 😉
Yes, this is a lesson we learn quite quickly (the hard way) if ever we have to port our application from one language or country to another.
Viewing 15 posts - 1 through 15 (of 22 total)
You must be logged in to reply to this topic. Login to reply