| title | Database Engine: Breaking Changes | |
|---|---|---|
| titleSuffix | SQL Server 2025 Preview | |
| description | Breaking changes to database engine features in SQL Server 2025 Preview. | |
| author | MikeRayMSFT | |
| ms.author | mikeray | |
| ms.reviewer | randolphwest | |
| ms.date | 08/19/2025 | |
| ms.service | sql | |
| ms.subservice | release-landing | |
| ms.topic | conceptual | |
| helpviewer_keywords |
|
|
| monikerRange | >=sql-server-2017 || >=sql-server-linux-2017 |
[!INCLUDE sqlserver2025]
This article describes the breaking changes to features in the SQL Server Database Engine introduced with [!INCLUDE sssql25-md]. These changes can break applications, scripts, or functionalities that are based on earlier versions of [!INCLUDE ssNoVersion].
[!INCLUDE sssql25-md] includes changes to encryption that introduce a breaking change to linked servers. These changes can break applications, scripts, or functionalities that are based on earlier versions of [!INCLUDE ssNoVersion]. You might encounter these issues when you upgrade.
In [!INCLUDE sssql25-md]:
- Linked servers to instances of SQL Server 2025 Preview must use the
Encryptparameter in the connection string - When you migrate from previous editions of SQL Server to SQL Server 2025 Preview with Microsoft OLE DB Driver 19, existing linked server configurations can fail
For information about how to connect securely to [!INCLUDE sssql25-md] instances, see TDS 8.0.
[!INCLUDE sssql25-md] includes changes to encryption that introduce a breaking change to Transactional, Snapshot, Peer to peer and Merge replication.
In [!INCLUDE sssql25-md]:
- In-place upgrades to SQL Server 2025 Preview for instances with a remote distributor can fail
- Adding a remote distributor to a SQL Server 2025 Preview publisher can fail
For information about how to connect securely to [!INCLUDE sssql25-md] instances, see TDS 8.0.
[!INCLUDE sssql25-md] includes changes to encryption that introduce a breaking change to log shipping. You might encounter these issues when you upgrade.
Log shipping monitoring can break if the monitor is a remote [!INCLUDE sssql25-md] instance when other SQL Server instances in the log shipping topology use a previous version.
For information about how to connect securely to [!INCLUDE sssql25-md] instances, see TDS 8.0.
[!INCLUDE sssql25-md] includes changes to encryption that introduce a breaking change to PolyBase. These changes might break applications, scripts, or functionalities that are based on earlier versions of [!INCLUDE ssNoVersion].
In [!INCLUDE sssql25-md]: