Summary
This update adds the CLR strict security feature to Microsoft SQL Server.
However, the feature is turned off for backward compatibility in SQL Server. Because of database level compatibility, the feature cannot be enabled by using the sp_configure 'clr strict security', 1 command.
To enable CLR strict security, add trace flag 6545 to the server Database Engine Service Startup Options. Remember that this trace flag can be used only together with SQL Server startup options. It cannot be set by using the DBCC TRACEON command.
More information
The fix for this update is included in the following cumulative updates and service pack for SQL Server:
Cumulative Update 7 for SQL Server 2016 RTM
Cumulative Update 4 for SQL Server 2016 Service Pack 1
Cumulative Update 6 for SQL Server 2014 SP2
Cumulative update 10 for SQL Server 2012 SP3
Service pack information for SQL Server
About SQL Server 2016 builds
Each new build for SQL Server 2016 contains all the hotfixes and all the security fixes that were included with the previous build. We recommend that you install the latest build for SQL Server:
latest build for SQL Server 2016.
Service packs are cumulative. Each new service pack contains all the fixes that are in previous service packs, together with any new fixes. Our recommendation is to apply the latest service pack and the latest cumulative update for that service pack. You do not have to install a previous service pack before you install the latest service pack. Use Table 1 in the following article for finding more information about the latest service pack and latest cumulative update.
How to determine the version, edition and update level of SQL Server and its components
References
Learn about the terminology Microsoft uses to describe software updates.
