Skip to content

Latest commit

 

History

History
54 lines (41 loc) · 3.26 KB

File metadata and controls

54 lines (41 loc) · 3.26 KB
title Breaking Changes to Database Engine Features in SQL Server 2016 | Microsoft Docs
ms.custom
ms.date 11/15/2016
ms.prod sql
ms.prod_service database-engine
ms.service
ms.component database-engine
ms.reviewer
ms.suite sql
ms.technology
database-engine
ms.tgt_pltfrm
ms.topic conceptual
helpviewer_keywords
Database Engine [SQL Server], what's new
breaking changes [SQL Server]
ms.assetid 47edefbd-a09b-4087-937a-453cd5c6e061
caps.latest.revision 144
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.

  • Using the MD2, MD4, MD5, SHA, or SHA1 hash algorithms (not recommended) requires setting the database compatibility level to earlier 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, refer to this Microsoft Support Article.

Previous Versions

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