Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««12

Datetime precision Expand / Collapse
Author
Message
Posted Monday, November 30, 2009 7:23 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Today @ 7:30 AM
Points: 2,947, Visits: 243
Obviously I can't read. I didn't see that .100 hanging out there!!!
Post #826190
Posted Monday, November 30, 2009 8:23 AM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Today @ 2:13 PM
Points: 31,040, Visits: 15,472
the dateadd is not commented out, just the note.

SQL is only precise to .0, .3, and .7ms, therefore you can't have .1 as the answer. It could only be one of those 3







Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #826237
Posted Monday, November 30, 2009 8:37 AM


SSChasing Mays

SSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing Mays

Group: General Forum Members
Last Login: Friday, January 3, 2014 10:59 AM
Points: 626, Visits: 836
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
Post #826252
Posted Monday, November 30, 2009 8:38 AM
SSChasing Mays

SSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing Mays

Group: General Forum Members
Last Login: Monday, July 7, 2014 8:58 AM
Points: 654, Visits: 400
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!
Post #826255
Posted Monday, November 30, 2009 9:38 AM
Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Friday, August 22, 2014 9:27 AM
Points: 717, Visits: 689
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.
Post #826314
Posted Wednesday, December 2, 2009 8:38 AM


SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Friday, February 4, 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
Post #827555
Posted Thursday, December 10, 2009 10:22 PM


SSChasing Mays

SSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing Mays

Group: General Forum Members
Last Login: Friday, January 11, 2013 12:41 PM
Points: 621, Visits: 297
I am confused !



Bhavesh Patel

http://bhaveshgpatel.wordpress.com/
Post #832720
Posted Wednesday, June 11, 2014 4:55 PM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Today @ 7:30 AM
Points: 2,947, Visits: 243
Good to know.
Post #1579848
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse