Why 1753?

In SQL Server the minimum date that you can enter is the 1st of January 1753. If you are extracting data from SAP, as I’m doing, you will see this particular date if a null date is extracted. This date can then pop-up on a user report making any user to ask why 1753… Well the answer is quite interesting. The year 1753 was the first full year after Britain adopted the Gregorian Calendar (our current calendar), which was 11-day shorter than the Julian Calendar at that time.  More info here: http://en.wikipedia.org/wiki/January_1

And if you are even more curious to know why countries changed from the Julian Calendar to the Gregorian Calendar then you can read this: http://en.wikipedia.org/wiki/Gregorian_calendar

Tagged with:
Posted in SAP, SSIS
3 comments on “Why 1753?
  1. Ayman El-Ghazali says:

    I’ve had my share of fun with Julian date conversion from DB2 to SQL server. Nice to know the history behind it.

    • jbartual says:

      Maybe you can share your experience. Any recommended workaround?

      • We used to convert the date during our ETL Process. The T-SQL Code to convert from Julian dates is:
        DATE(DIGITS(DECIMAL([YourDateField] + 1900000,7,0)))

        I used to have a function that would convert the reverse way. I’m on vacation now but I’ll look it up when I get back.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 24 other followers

%d bloggers like this: