Two digit year cutoff in SQL Server 2008 R2

Question

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

Answer 1

Import the string dates into DATE/DATETIME format.
DATE/DATETIME has 4 digit year.
You can convert it differently than the automatic 2049 flip year.
DATE/TIME functions & string conversions:
http://www.sqlusa.com/bestpractices/datetimeconversion/
Here is an automatic conversion example.
DECLARE @StringDate char(8) = '10/23/80';
DECLARE @Date DATE;
SELECT @Date=CONVERT(date, @StringDate, 1);
SELECT @Date;
-- 1980-10-23
Kalman Toth Database & OLAP Architect
SQL Server 2014 Database Design
New Book / Kindle: Beginner Database Design & SQL Programming Using Microsoft SQL Server 2014