breaking-changes-to-database-engine-features-in-sql-server-2016.md

title	Breaking Changes to Database Engine Features in SQL Server 2016 | Microsoft Docs
ms.custom
ms.date	11/27/2016
ms.prod	sql
ms.prod_service	high-availability
ms.reviewer
ms.technology	release-landing
ms.topic	conceptual
helpviewer_keywords	Database Engine [SQL Server], what's new breaking changes [SQL Server]
ms.assetid	47edefbd-a09b-4087-937a-453cd5c6e061
author	MikeRayMSFT
ms.author	mikeray
manager	craigg

Breaking Changes to Database Engine Features in SQL Server 2016

[!INCLUDEtsql-appliesto-ss2016-xxxx-xxxx-xxx-md]

This topic describes breaking changes in the [!INCLUDEssCurrent] [!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]

• The sample_ms column of sys.dm_io_virtual_file_stats has expanded from an int to a bigint data type.

• The TimeStamp column of sys.fn_virtualfilestats has expanded from an int to a bigint data type.

• The MD2, MD4, MD5, SHA, and SHA1 algorithms are not available under compatibility level 130. Using the MD2, MD4, MD5, SHA, or SHA1 hash algorithm is not recommended, but can be done by setting the database compatibility level to a value lower than 130.

• 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, DATEDIFF and ROUND. For more information, see this Microsoft Support Article.

Previous Versions

For information about breaking changes in [!INCLUDEssSQL14], and in some earlier versions, see Breaking Changes to Database Engine Features in SQL Server 2014.

Archived Documentation for Very Old Versions of SQL Server

[!INCLUDEArchived documentation for very old versions of SQL Server]

See Also

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