|
|
|
SSCommitted
      
Group: General Forum Members
Last Login: 2 days ago @ 7:52 AM
Points: 1,710,
Visits: 61
|
|
| Obviously I can't read. I didn't see that .100 hanging out there!!!
|
|
|
|
|
SSC-Dedicated
           
Group: Administrators
Last Login: Yesterday @ 1:47 PM
Points: 31,406,
Visits: 13,722
|
|
|
|
|
|
SSChasing Mays
      
Group: General Forum Members
Last Login: Monday, February 18, 2013 3:22 PM
Points: 626,
Visits: 835
|
|
jim.taylor (11/30/2009) I'm confused, if DateTime is only precise to 3.33 ms, why then is the answer just 1 ms off? Why not 3 ms?
SQL Server rounded down to 100 ms from the 101ms that was added. if you add 102ms it rounds up to 103 ms.
I posted this question because the inaccuracy caught me off guard a couple months ago when I kept getting unexpected results out of some code.
After suspecting sheer lunacy to be the root cause, I finally got the notion that maybe the SQL Server clock was dodgy. I wrote the query that you see in the question to test that theory and the BOL confirmed the rest.
To avoid the issue, use datetime2 which is more precise, but still has the same problem when you get down to 100 nanoseconds.
My issue was resolved by ignoring milliseconds since I didn't need to be that precise, and accuracy was more important than precision.
Thanks All!
~Craig
Craig Outcalt
Tips for new DBAs: http://www.sqlservercentral.com/articles/Career/64632 My other articles: http://www.sqlservercentral.com/Authors/Articles/Craig_Outcalt/560258
|
|
|
|
|
Mr or Mrs. 500
      
Group: General Forum Members
Last Login: Thursday, January 17, 2013 2:34 PM
Points: 565,
Visits: 360
|
|
jim.taylor (11/30/2009) ...if DateTime is only precise to 3.33 ms, why then is the answer just 1 ms off? Why not 3 ms? When the SELECT output's ms aspect can be one of 100 (from 99.9) or 103 (from 103.23), 100 is closer .
I chose the wrong answer because I was thinking of roundoff in 3ms increments instead of in 3.33ms increments (although I should have realized that the choice should then have been between 99 and 102 ), so thank you to the questioner!
|
|
|
|
|
Say Hey Kid
      
Group: General Forum Members
Last Login: Friday, April 26, 2013 11:57 AM
Points: 708,
Visits: 660
|
|
Based on all the comments here, I got completely lucky.
I assumed it was a trick question, and figured Midnight was one of those mystery values between today and yesterday, and that 1 millisecond was 'consumed' in the math. I'm clearly thinking way to hard about these QotDs.
|
|
|
|
|
SSC Eights!
      
Group: General Forum Members
Last Login: Friday, February 04, 2011 7:20 AM
Points: 977,
Visits: 1,499
|
|
peter.house (11/30/2009) While looking at the answer choices, my brain kept saying "Yesterday Midnight + 100ms"
For me, Midnight today is tonight and the SQL answer is this morning at 100ms after midnight or 100ms after the beginning of day.
The time element for midnight is 0, not 24. If it were 24 then the answer would have been 101 ms after midnight (tomorrow morning).
Tom Garth Vertical Solutions
"There are three kinds of men. The one that learns by reading. The few who learn by observation. The rest of them have to pee on the electric fence for themselves." -- Will Rogers
|
|
|
|
|
SSChasing Mays
      
Group: General Forum Members
Last Login: Friday, January 11, 2013 12:41 PM
Points: 621,
Visits: 297
|
|
|
|
|