| title | Breaking Changes to Database Engine Features in SQL Server 2017 | Microsoft Docs | |
|---|---|---|
| description | Breaking changes to Database Engine Features in SQL Server 2017 | |
| ms.date | 04/19/2017 | |
| ms.prod | sql-vnext | |
| ms.reviewer | ||
| ms.suite | ||
| ms.technology |
|
|
| ms.tgt_pltfrm | ||
| ms.topic | article | |
| helpviewer_keywords |
|
|
| ms.assetid | ||
| caps.latest.revision | 1 | |
| author | BYHAM | |
| ms.author | rickbyh | |
| manager | jhubbard |
Breaking Changes to Database Engine Features in [!INCLUDEsssqlv14-md]
[!INCLUDEtsql-appliesto-ssvnxt-xxxx-xxxx-xxx]
This topic describes breaking changes in the [!INCLUDEsssqlv14-md][!INCLUDEssDE]. 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 [!INCLUDEsssqlv14-md][!INCLUDEssDE]
- CLR uses Code Access Security (CAS) in the .NET Framework, which has been marked as obsolete. A CLR assembly created with
PERMISSION_SET = SAFEmay be able to access external system resources, call unmanaged code, and acquire sysadmin privileges. Beginning with [!INCLUDEsssqlv14-md], ansp_configureoption calledclr strict securityis introduced to enhance the security of CLR assemblies.clr strict securityis enabled by default, and treatsSAFEandEXTERNAL_ACCESSassemblies as if they were markedUNSAFE. Theclr strict securityoption can be disabled for backward compatibility, but this is not recommended. Microsoft recommends that all assemblies be signed by a certificate or asymmetric key with a corresponding login that has been grantedUNSAFE ASSEMBLYpermission in the master database. For more information, see CLR strict security.
-
Breaking Changes to Database Engine Features in SQL Server 2016
-
Breaking Changes to Database Engine Features in SQL Server 2014
-
Breaking Changes to Database Engine Features in SQL Server 2012
-
Breaking Changes to Database Engine Features in SQL Server 2008
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)