SQL 2008, one of the big ones, as far as I am concerned, is the newly accurate datetime datatypes  (ie datetime2, date, time, etc.)

I understand we've got precision to 100 nanoseconds with DATETIME2.  
I wasn't sure about DATETIME itself, and whether it still has an accuracy of 3.33 milliseconds.

Does it?
LVL 17
Who is Participating?
Guy Hengel [angelIII / a3]Connect With a Mentor Billing EngineerCommented:
yes, that's still the same.
dbaSQLAuthor Commented:
I should have been a little more detailed.  I am in the process of partioning some tables by datetime.  The function is DATETIME, but the table def is DATETIME2 as I am hoping to avoid the inaccuracies we have with v2000, and quit rounding the dates.

So I'm trying to determine if both the function and the table should be DATETIME, or DATETIME2.

Guy Hengel [angelIII / a3]Billing EngineerCommented:
I would use DATETIME2, as accuracy is of concern
Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

dbaSQLAuthor Commented:
agreed.  thank you, angellll
Daniel WilsonCommented:
just some links to back up what AngelIII says:  -- datetime "Accuracy                        -- Rounded to increments of .000, .003, or .007 seconds"

Discussion of DateTime, DateTime2, Date, and Time:
dbaSQLAuthor Commented:
I've seen the 1st one, but I'll check out the latter.  Thanks much.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.