TechNet
Export (0) Print
Expand All

Breaking Changes to Database Engine Features in SQL Server 2016

 

Updated: August 16, 2016

THIS TOPIC APPLIES TO: yesSQL Server (starting with 2016)noAzure SQL DatabasenoAzure SQL Data Warehouse noParallel Data Warehouse

This topic describes breaking changes in the SQL Server 2016Database Engine and earlier versions of SQL Server. These changes might break applications, scripts, or functionalities that are based on earlier versions of SQL Server. You might encounter these issues when you upgrade.

  • 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.

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)

Community Additions

ADD
Show:
© 2016 Microsoft