| title | titleSuffix | description | author | ms.author | ms.reviewer | ms.date | ms.service | ms.subservice | ms.topic | helpviewer_keywords | monikerRange | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
Database Engine: Breaking changes |
SQL Server 2017 |
Learn about changes that might break applications, scripts, or functionalities that are based on earlier versions of SQL Server. |
MikeRayMSFT |
mikeray |
randolphwest |
08/02/2024 |
sql |
release-landing |
conceptual |
|
>=sql-server-2017 || >=sql-server-linux-2017 |
[!INCLUDE SQL Server 2017]
This article describes breaking changes in the [!INCLUDE sssql17-md] [!INCLUDE ssDE]. These changes might break applications, scripts, or functionalities that are based on earlier versions of [!INCLUDE ssNoVersion]. You might encounter these issues when you upgrade.
[!INCLUDE code-access-security]
The MD2, MD4, MD5, SHA, and SHA1 algorithms are deprecated in [!INCLUDE sssql15-md]. Up to [!INCLUDE sssql15-md], a self-signed certificate is created using SHA1. Starting with [!INCLUDE ssSQL17], a self-signed certificate is created using SHA2_256.
- Breaking changes to Database Engine features in SQL Server 2016
- Breaking Changes to Database Engine Features in SQL Server 2014
[!INCLUDE previous-versions-archive-documentation-sql-server]