| title | Database Engine: Breaking changes | ||
|---|---|---|---|
| titleSuffix | SQL Server 2016 | ||
| description | Learn about Database Engine changes in SQL Server 2016 (13.x) and earlier that might break previous-version functionality when you upgrade. | ||
| author | MikeRayMSFT | ||
| ms.author | mikeray | ||
| ms.reviewer | randolphwest | ||
| ms.date | 07/25/2022 | ||
| ms.prod | sql | ||
| ms.prod_service | high-availability | ||
| ms.technology | release-landing | ||
| ms.topic | conceptual | ||
| ms.custom | seo-lt-2019 | ||
| helpviewer_keywords |
|
[!INCLUDE SQL Server 2016]
This article describes breaking changes in the [!INCLUDEsssql15-md] [!INCLUDEssDE] and earlier versions of [!INCLUDEssNoVersion]. These changes might break applications, scripts, or functionalities that are based on earlier versions of [!INCLUDEssNoVersion]. You might encounter these issues when you upgrade.
Breaking Changes in [!INCLUDEsssql15-md]
-
The sample_ms column of
sys.dm_io_virtual_file_statshas expanded from an int to a bigint data type. -
The TimeStamp column of
sys.fn_virtualfilestatshas expanded from an int to a bigint data type. -
Under database compatibility level 130, implicit conversions from datetime to datetime2 data types show improved accuracy by accounting for the fractional milliseconds, resulting in different converted values. Use explicit casting to datetime2 datatype whenever a mixed comparison scenario between datetime and datetime2 datatypes exists. For more information, see this Microsoft Support Article.
-
Under database compatibility level 130, operations that perform implicit conversions between certain numeric and datetime data types show improved accuracy and can result in different converted values. This includes usage of functions that require calculations such as, for example,
DATEDIFFandROUND. For more information, see this Microsoft Support Article.
For information about breaking changes in [!INCLUDEssSQL14], and in some earlier versions, see Breaking Changes to Database Engine Features in SQL Server 2014.
[!INCLUDEArchived documentation for very old versions of SQL Server]
- Deprecated Database Engine Features in SQL Server 2016
- Discontinued Database Engine Functionality in SQL Server 2016
- SQL Server Database Engine Backward Compatibility
- ALTER DATABASE Compatibility Level (Transact-SQL)
- SQL Server 2016 or SQL Server 2017 on Windows improvements in handling some data types and uncommon operations