Cumulative Update 6 for SQL Server 2016 SP2

Applies to: SQL Server 2016 DeveloperSQL Server 2016 EnterpriseSQL Server 2016 Enterprise Core

This article describes Cumulative Update package 6 (CU6) (build number: 13.0.5292.0) 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.

Cumulative update

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 with the previous CU for the installed version/Service Pack of SQL Server.
  • 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


The following update is available from the Microsoft Download Center:
 
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


VSTS bug number KB article number Description Fix area
12710423

4500327    

FIX: Non-yielding scheduler issue occurs when you run queries in batch-mode that spill in SQL Server 2016

SQL Engine
12186150 4468101

Improvement: Optional replacement for "String or binary data would be truncated" message with extended information in SQL Server 2016 and 2017

SQL Engine
12748064 4480652 FIX: SQL Writer Service can cause undetected deadlocks on system DMV when you do a VSS backup SQL Engine
12671862 4486932 FIX: Users are incorrectly permitted to create incremental statistics on nonclustered indexes which are not aligned to the base table in SQL Server 2016 SQL performance
12600924 4488403 FIX: Images in the report will not display when the report name contains a bracket "(" in SSRS 2016 Reporting services
12646096 4488809 FIX: Assertion occurs when a parallel query deletes from a Filestream table in SQL Server 2014 and 2016 SQL Engine
12668586 4488817 FIX: FILESTREAM for file I/O access feature can't be enabled when you use Cluster Shared Volumes (CSV) in SQL Server 2016 Failover Cluster Instances SQL Engine
12658209 4488853 FIX: 'MSrepl_agent_jobs' does not exist when you run sp_addpullsubscription_agent to create pull subscription in SQL Server 2016 SQL Engine
12639882 4488856 FIX: Error 2812 and 20028 occur when you drop publisher or enable database for publication after you upgrade your SQL Server 2016 SQL Engine
12654426 4488949 FIX: Assertion occurs when linked server which points to itself is used in a cross-database transaction in SQL Server 2016 SQL Engine
12654303 4488971 FIX: MDS database upgrade fails with error in SQL Server 2016 Data Quality Services (DQS)
12660793 4489202 FIX: Error 10314 occurs when you load .NET CLR assembly in SQL Server 2016 database SQL Engine
12677809 4490138 FIX: Filtered NCI over a CCI may not be maintained when the table is updated in a way that none of the key or included columns of the NCI are changed SQL performance
12673166 4490140 FIX: Stack Dump occurs in the change tracking cleanup process in SQL Server 2016 SQL Engine
12391094 4490141 Improvement: DMV sys.dm_hadr_cluster reports cloud witness quorum type "4" and quorum_type_desc "UNKNOWN_QUORUM" in SQL Server 2016 High Availability
12708933 4490435 FIX: "The given key was not present in the dictionary" occurs if you do a preview in the CDC Source in SQL Server 2016 Integration services
12700350 4490737 FIX: Unable to edit a Data-Driven subscription with date parameter in SSRS 2016 Reporting services
12689122 4490743 FIX: Simple Data Grid row header disappears when an item within the grid is clicked in SSRS 2016 Reporting services
12664995 4491333 FIX: Subscription will fail if the DateTime parameter is created and edited by different locale and keyboard language in SSRS 2016 Reporting services
12722975 4492762 FIX: SQL Trace Collection Set fails when you click "Collect and Upload Now" in SQL Server 2016 SQL Engine
12679390 4492865 Improvement: You can use JQuery 3.0.0 or later versions in SSRS 2016 Reporting services
12711556 4492880 FIX: Automatic seeding assertions when databases are removed from AG in SQL Server 2016 High Availability
12741001 4492899 FIX: FileTable database level directory is inaccessible after database startup in SQL Server 2016 SQL Engine
12644636 4493329 FIX: Error occurs when sp_addarticle is used to add article for transactional replication to memory-optimized table on subscriber in SQL Server 2016 SQL Engine
12738723 4493363 FIX: A specially crafted query run by a low privileged user may expose the masked data in SQL Server 2016 SQL security
12733996 4493364 FIX: Error occurs when you back up a virtual machine with non-component based backup in SQL Server 2016 SQL Engine

Notes for this update


Hybrid environments deployment

When you deploy the hotfixes to a hybrid environment (such as AlwaysOn, replication, cluster, and mirroring), we recommend that you refer to the following articles before you deploy the update:
 

Cumulative update package information


Prerequisites

To apply this cumulative update package, you must be running SQL Server 2016 SP2.

Restart information

You may have to restart the computer after you apply this cumulative update package.

Registry information

To use one of the hotfixes in this package, you do not have to make any changes to the registry.