March 9, 2013 at 6:27 pm
Comments posted to this topic are about the item DATETIME - 3
March 9, 2013 at 11:04 pm
This was a tough one for me. I didn't know the default cut off year. thanks.
--------------------------------------------------------------------------------------
Hai Ton
My Db4Breakfast blog.
March 10, 2013 at 12:57 am
Thank Ron
Thanks
Vinay Kumar
-----------------------------------------------------------------
Keep Learning - Keep Growing !!!
March 10, 2013 at 1:01 am
Thanks Ron for question. i learn something new !!!. π
Thanks
Vinay Kumar
-----------------------------------------------------------------
Keep Learning - Keep Growing !!!
March 10, 2013 at 3:05 pm
Nice question and good explanation. Thanks Ron.
Tom
March 10, 2013 at 10:48 pm
L' Eomot InversΓ© (3/10/2013)
Nice question and good explanation. Thanks Ron.
+1
I marked it too soon π
too soon to be correct π
~ demonfox
___________________________________________________________________
Wondering what I would do next , when I am done with this one :ermm:
March 10, 2013 at 11:15 pm
Thanks Ron.
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
March 10, 2013 at 11:19 pm
db4breakfast (3/9/2013)
This was a tough one for me. I didn't know the default cut off year. thanks.
+1
something new for me to learn as well.
Thanks Ron!
~ Lokesh Vij
Link to my Blog Post --> www.SQLPathy.com[/url]
Follow me @Twitter
March 11, 2013 at 12:57 am
Hi,
can someone plz explain it in a more simple manner..... explanation in QOTD is very inscrutable for me:cool:
_______________________________________________________________
To get quick answer follow this link:
http://www.sqlservercentral.com/articles/Best+Practices/61537/
March 11, 2013 at 1:47 am
kapil_kk (3/11/2013)
Hi,can someone plz explain it in a more simple manner..... explanation in QOTD is very inscrutable for me:cool:
Inscrutable , is that the right word :ermm:
well, as explained in the explanation ..
1.
The two digit year cutoff option specifies an integer from 1753 to 9999 that represents the cutoff year for interpreting two-digit years as four-digit years.
So, for sql server to interpret Two digit year as Four digit year
2.
The default time span for SQL Server is 1950-2049,
It means , if you anything in between the above range .. it will interpret as current century ..
50 is 1950
51 is 1951
49 is 2049
48 is 2048
is that clear enough ??? π
~ demonfox
___________________________________________________________________
Wondering what I would do next , when I am done with this one :ermm:
March 11, 2013 at 2:35 am
thanks for the explanation....
Previously I didn't check the link.. after reading explanation I check that link and read that fully and its clear my doubts..
Thanks Ron for the question that make me learn new thing today :-):-)
_______________________________________________________________
To get quick answer follow this link:
http://www.sqlservercentral.com/articles/Best+Practices/61537/
March 11, 2013 at 2:55 am
Thank you for a nice one question.
March 11, 2013 at 3:27 am
Thank you for the question. I got it right as I knew this. π
(and I was expecting to see this "2050-01-27" as one of the answers for value-2)
ww; Raghu
--
The first and the hardest SQL statement I have wrote- "select * from customers" - and I was happy and felt smart.
March 11, 2013 at 4:05 am
This was removed by the editor as SPAM
March 11, 2013 at 4:56 am
Good question on a feature that, hopefully, nobody ever relies on anymore. π
Minor issues: it looks like the distracter options for value 1 and value 2 have been switched, and there was only one answer option for value 4.
Viewing 15 posts - 1 through 15 (of 37 total)
You must be logged in to reply to this topic. Login to reply