This article describes Cumulative Update package 14 (CU14) (build number: 13.0.5830.85) for Microsoft SQL Server 2016 Service Pack 2 (SP2). This update contains fixes that were released after the initial release of SQL Server 2016 SP2.
About cumulative updates for SQL Server
Cumulative updates (CU) are now available at the Microsoft Download Center.
Only the most recent CU that was released for SQL Server 2016 SP2 is available at the Download Center. Each new CU contains all the fixes that were included togetrher with the previous CU for the installed version or service pack of SQL Server. For a list of the latest cumulative updates for SQL Server, see the following article:
- Microsoft recommends ongoing, proactive installation of CUs as they become available:
- SQL Server CUs are certified to the same levels as Service Packs, and should be installed at the same level of confidence.
- Historical data shows that a significant number of support cases involve an issue that has already been addressed in a released CU.
- CUs may contain added value over and above hotfixes. This includes supportability, manageability, and reliability updates.
- Just as for SQL Server service packs, we recommend that you test CUs before you deploy them to production environments.
- We recommend that you upgrade your SQL Server installation to the latest SQL Server 2016 service pack.
How to obtain this cumulative update package
If the download page does not appear, contact Microsoft Customer Service and Support to obtain the cumulative update package.
Note After future cumulative updates are released for SQL Server 2016, this CU can be located and downloaded from the Microsoft Windows Update Catalog. However, we recommend that you always install the latest cumulative update that is available.
Additional hotfixes that are included in this cumulative update package
|Bug reference||KB article number||Description||Fix area||Platform|
|13544150||This improvement includes object level lock optimization on secondary replicas of AlwaysOn Availability Groups and addresses the schema lock contention on secondary replica redo, especially when the number of logical processors is large.||High Availability||Windows|
|13573411||Fixes an access violation exception when you execute "insert into <table> exec sp_execute_external_script" statement and the table has an identity column in SQL Server 2016.||SQL Engine||All|
|12929737||4576757||FIX: Access violation occurs when you query cloned database in SQL Server 2016||SQL Engine||Windows|
|13378995||4568447||FIX: Automatic seeding failure occurs for a secondary replica in SQL Server 2016||High Availability||Windows|
|13516059||4571296||Improvement: Option to forcefully turn QDS off by specifying the additional option in ALTER DB command||SQL Engine||Windows|
|13529589||4575939||FIX: Log reader agent generates access violation exception for P2P or transactional replication with partitioning tables in SQL Server 2016||SQL Engine||Windows|
|13539976||Executing sys.fn_xe_file_target_read_file may cause an Access violation in SQL Server 2016.||SQL Engine||Windows|
|13560933||Fixes an access violation which occurs while querying row mod count property on spatial indexes in SQL Server 2016.||SQL performance||Windows|
|13561178||Fixes deadlocks that occur in [catalog].[set_execution_property_override_value].||Integration Services||Windows|
|13567427||Fixes intermittent "Unexpected Exception" error that is encountered when using SQL Dialect against SSAS Tabular.||Analysis Services||Windows|
|13575425||4568653||FIX: INSERT EXEC doesn't work when you insert row containing explicit identity value into table with IDENTITY column and IDENTITY_INSERT is OFF by default in SQL Server||SQL Engine||Windows|
|13587428||Fixes indefinite hang during cube processing caused by connection throttling. This problem only occurs after applying Cumulative Update 7 (CU7) for SQL Server Analysis Services 2016 Service Pack 2 (SP2).||Analysis Services||Windows|
|13596467||4569837||FIX: Intermittent connection error occurs when an expression is used for both connection string and password of a connection manager||Integration Services||Windows|
|13606996||4575940||FIX: Newly added articles' snapshot doesn't get applied to subscriber in SQL Server 2016||SQL Engine||Windows|
|13616653||4547890||FIX: ISDBUpgradeWizard.exe throws error when you try to upgrade SSISDB after restoring from earlier versions in SQL Server||Integration Services||Windows|
RSetup.exe is updated to version 188.8.131.525. This new version downloads new SRS_184.108.40.2068_1033.cab and SRO_220.127.116.117_1033.cab CAB files. This update will install a new version of R 3.5, and configure it to be the default version in new installations.
An updated RegisterRext.exe that accepts the /configure and /cleanup command-line options to do the respective customer-requested actions is shipping together with the new R CAB files. To configure R 3.5 as the default version of R, or to clean up an unused old runtime in an existing installation by using this RegisterRext.exe, follow the instructions at https://go.microsoft.com/fwlink/?linkid=2133077.
Notes for this update
Hybrid environments deployment
- SQL Server failover cluster rolling update and service pack process.
Note If you don't want to use the rolling update process, follow these steps to apply an update:
- Install the update on the passive node.
- Install the update on the active node (requires a service restart).
- Upgrade and update of availability group servers that use minimal downtime and data loss.
Note If you enabled AlwaysOn with SSISDB catalog, see the information about SSIS with AlwaysOn for more information about how to apply an update in these environments.
- How to apply a hotfix for SQL Server in a transactional replication and database mirroring topology
- How to apply a hotfix for SQL Server in a replication topology
- How to install service packs and hotfixes on an instance of SQL Server that is configured to use database mirroring
- Overview of SQL Server Servicing Installation
Cumulative update package information
To apply this cumulative update package, you must be running SQL Server 2016 SP2.
You may have to restart the computer after you apply this cumulative update package.
To use one of the hotfixes in this package, you do not have to make any changes to the registry.
- Announcing updates to the SQL Server Incremental Servicing Model (ISM)
- How to obtain the latest service pack for SQL Server 2016
- The script to determine which version and edition of SQL Server Database Engine is running
- The Incremental Servicing Model for SQL Server to deliver hotfixes for reported problems
- Naming schema for Microsoft SQL Server software update packages
- Description of the standard terminology that is used to describe Microsoft software updates