In The Beginning

Question

Post reply

In The Beginning

Viewing 15 posts - 16 through 30 (of 39 total)

You must be logged in to reply to this topic. Login to reply

paul.knibbs SSCoach Points: 15320 More actions · Answer 1

Mike Hays (11/25/2014)
I could swore that it was sometime in 1975?

So you've never stored a date prior to 1975 in a DATETIME? :blink:

Ed Wagner SSC Guru Points: 287026 More actions · Answer 2

paul.knibbs (11/25/2014)
Mike Hays (11/25/2014)
I could swore that it was sometime in 1975?
So you've never stored a date prior to 1975 in a DATETIME? :blink:

Or what that your personal beginning of time?

select DATEADD(week, -38, '01/01/1975');

Tally Tables - Performance Personified
String Splitting with True Performance
Best practices on how to ask questions

Mike Hays SSCommitted Points: 1871 More actions · Answer 3

Maybe its me. Once I had BASIC loaded on my Altair 8800, I can not seem to remember anything before that (like my wedding, children being born, Jets winning the Super Bowl).

dlaughlin 24148 Old Hand Points: 355 More actions · Answer 4

Mike Hays (11/25/2014)
Maybe its me. Once I had BASIC loaded on my Altair 8800, I can not seem to remember anything before that (like my wedding, children being born, Jets winning the Super Bowl).

The Jets? LOL! As if THAT could have ever happened.

stephen.long.1 SSCrazy Points: 2582 More actions · Answer 5

Thanks for the nice, easy question, Sean.

Another good option for the list of choices would have 0001-01-01, which is the earliest date for a DateTime2 data type.

I thought that perhaps 1975-04-04 was Steve Jones' birthday. 😀

webrunner SSC-Dedicated Points: 31859 More actions · Answer 6

"3114 B.C. is the start of the Mayan calendar."

I wonder whether the Mayans used "May-SQL" 😀

- webrunner

-------------------
A SQL query walks into a bar and sees two tables. He walks up to them and asks, "Can I join you?"
Ref.: http://tkyte.blogspot.com/2009/02/sql-joke.html

SQLRNNR SSC Guru Points: 281334 More actions · Answer 7

I love the error that is thrown trying to generate any date prior to 1753 from a datetime data type.

Adding a value to a 'datetime' column caused an overflow.

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

stephen.long.1 SSCrazy Points: 2582 More actions · Answer 8

Mike Hays (11/25/2014)
Maybe its me. Once I had BASIC loaded on my Altair 8800, I can not seem to remember anything before that (like my wedding, children being born, Jets winning the Super Bowl).

Hmm, maybe that's why I can't remember the Vikings ever winning the Super Bowl. Oh, wait... 🙁

stephen.long.1 SSCrazy Points: 2582 More actions · Answer 9

webrunner (11/25/2014)
"3114 B.C. is the start of the Mayan calendar."
I wonder whether the Mayans used "May-SQL" 😀
- webrunner

+1 :w00t:

PHYData DBA SSCertifiable Points: 7541 More actions · Answer 10

I see so many posts thanking the Author for an easy question.

I also see 49% of the answers are for 1900-01-01....

Human Irony and Dichotomy United!

PHYData DBA SSCertifiable Points: 7541 More actions · Answer 11

Brian.Klinect (11/25/2014)
That's exactly what I did. I had no idea I could use a negative number for a datetime!

Since DateTime is stored as an Integer, it only makes sense to use the Positive and Negative Values.

Anything thing else would be wasteful.

Ed Wagner SSC Guru Points: 287026 More actions · Answer 12

PHYData DBA (11/25/2014)
Brian.Klinect (11/25/2014)
That's exactly what I did. I had no idea I could use a negative number for a datetime!
Since DateTime is stored as an Integer, it only makes sense to use the Positive and Negative Values.
Anything thing else would be wasteful.

Actually, it's stored as two integers. The first one is the date and the second one is the time. I completely agree that not using the full range of the date integer would be wasteful. It's actually pretty efficient and works well.

Tally Tables - Performance Personified
String Splitting with True Performance
Best practices on how to ask questions

SQL_Hunt SSC-Dedicated Points: 33518 More actions · Answer 13

SQL_Hunt

SSC-Dedicated

Points: 33518

November 25, 2014 at 8:52 am

#1760850

Simple and nice informative question!!

Thanks.

kherald69 SSC Eights! Points: 971 More actions · Answer 14

Ed Wagner (11/25/2014)
PHYData DBA (11/25/2014)
Brian.Klinect (11/25/2014)
That's exactly what I did. I had no idea I could use a negative number for a datetime!
Since DateTime is stored as an Integer, it only makes sense to use the Positive and Negative Values.
Anything thing else would be wasteful.
Actually, it's stored as two integers. The first one is the date and the second one is the time. I completely agree that not using the full range of the date integer would be wasteful. It's actually pretty efficient and works well.

Actually, it is stored as a float. The whole number is the date and the fraction is the time.

Michael_Garrison Hall of Fame Points: 3110 More actions · Answer 15

Yep, that's me, guilty, not reading the question thoroughly and not getting my coffee first.