Remember the millenium bug fiasco. It happenned in Year 2000.
This is what chronicled in Wikipedia:
"The Year 2000 problem is also known as the Y2K problem, the Millennium bug, the Y2K bug, or Y2K. Problems resulted because people, including programmers, reduced the four-digit year to two digits. This made the year 2000 indistinguishable from 1900"
Now we have a better interpretation for people using two digit years as far as SQL Server is concerned.
The default time span for SQL Server is 1950-2049.
Two-digit year 49 is 2049, but two digit year 50 is back to 1950.
Probably you will start seeing it in your credit cards (may be?)
You may configure it in SQL Server 2017 using,
Exec Sp_Configure 'two digit year cutoff', 2038
In SQL Server 2012 Express it is enabled by default:
Read more here:
https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/configure-the-two-digit-year-cutoff-server-configuration-option
This is what chronicled in Wikipedia:
"The Year 2000 problem is also known as the Y2K problem, the Millennium bug, the Y2K bug, or Y2K. Problems resulted because people, including programmers, reduced the four-digit year to two digits. This made the year 2000 indistinguishable from 1900"
Now we have a better interpretation for people using two digit years as far as SQL Server is concerned.
The default time span for SQL Server is 1950-2049.
Two-digit year 49 is 2049, but two digit year 50 is back to 1950.
Probably you will start seeing it in your credit cards (may be?)
You may configure it in SQL Server 2017 using,
Exec Sp_Configure 'two digit year cutoff', 2038
In SQL Server 2012 Express it is enabled by default:
Read more here:
https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/configure-the-two-digit-year-cutoff-server-configuration-option
No comments:
Post a Comment