Quantcast
Viewing all articles
Browse latest Browse all 7696

Two digit year cutoff in SQL Server 2008 R2

Hi All,

We have a 2008R2 setup here and have SSIS jobs importing data from flat files into our database. Some sources only give us 2 digit years unfortunately. 

Looking at some data, the default 2 digit year cutoff  is not really appropriate to our setup, a value of 2080 would be better. However, when checking the official documentation here:

http://msdn.microsoft.com/en-us/library/ms191004(v=sql.105).aspx

there is a warning to leave the value alone to maintain backwards compatibility. This warning is NOT present for the newer versions of SQL Server. Is this just a generic warning about the general application landscape, or is there some Microsoft code somewhere within SQL Server/SSIS/SSRS which assumes this default is locked to 2049? In other words, if I understand the application landscape at my office - am I safe to change this? Or is there some underlying code which will break?

Also, am I right in the assumption that once a 2 digit year is imported into a database table, it's then converted to a 4 digit year, so any existing data is "safe" from this setting being changed? In other words, the DB loses all memory of whether an imported date was originally imported as a 2 digit year?

Thanks


Viewing all articles
Browse latest Browse all 7696

Trending Articles