Cumulative Update 7 for SQL Server 2016 SP2

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

This article describes Cumulative Update package 7 (CU7) (build number: 13.0.5337.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
12865856 4338636    FIX: SQL jobs fail due to blocking in SSISDB in SQL Server 2014 and 2016 Integration Services
12809383 4488036 FIX: Repl_Schema_Access wait issues when there are multiple publisher databases on the same instance of SQL Server 2016 SQL Engine
12822163 4489150 FIX: Filtered index may be corrupted when you rebuild index in parallel in SQL Server 2014 and 2016 SQL performance
12673144 4490136 FIX: Assertion error occurs when you use sys.dm_exec_query_statistics_xml in SQL Server 2016 SQL performance
12722070 4491560 FIX: Access violation occurs when you query sys.dm_hadr_availability_replica_states in SQL Server 2016 High Availability
12819451 4491696 FIX: Floating point exception error 3628 occurs when you query DMV sys.dm_db_xtp_hash_index_stats in SQL Server 2016 In-Memory OLTP
12639785 4492604 FIX: Manual failover between forwarder and secondary replica fails with all replicas synchronized in SQL Server 2016 High Availability
12931646 4493364 FIX: Error occurs when you back up a virtual machine with non-component based backup in SQL Server 2016 SQL Engine
12770729 4493765 FIX: HTML files cannot be opened directly from the web portal in SSRS 2016 Reporting Services
12783210 4494225 FIX: Access violation occurs when you run a query against sys.availability_replicas in SQL Server 2016 High Availability
12796269 4494805 FIX: Adding new Publication may fail if distribution database is in AG and collation is set to BIN in SQL Server 2016 SQL Engine
12801855 4495547 FIX: Remote ad hoc queries that use OPENDATASOURCE produce an incorrect error message when the new OLE DB provider is used SQL Engine
12800325 4497222 FIX: Database may crash when multiple threads update permissions on the same database in SQL Server 2016 Analysis Services
12816588 4497225 FIX: Query against table with both clustered columnstore index and nonclustered rowstore index may return incorrect results in SQL Server 2016 SQL Engine
12865860 4497230 FIX: Fail to join the secondary replica if the database has a defunct filegroup in SQL Server 2014 and 2016 High Availability
12865876 4497701 FIX: Columnstore filter pushdown may return wrong results when there is an overflow in filter expressions in SQL Server 2014 and 2016 SQL Engine
12748363 4497928 FIX: Indirect checkpoints on tempdb database cause "Non-yielding scheduler" error in SQL Server 2016 SQL Engine
12865873 4499231 FIX: Log reader agent may fail after AG failover with TF 1448 enabled in SQL Server 2014 and 2016 SQL Engine
12866582 4500403 FIX: Tlog grows quickly when you run auto cleanup procedure in SQL Server 2016 SQL Engine
12860702 4500770 FIX: AG is suspended when cross-database transaction is applied on AG databases in SQL Server 2016 High Availability
12750695 4501052 Improvement: Enable PDW APS to access TRY_CONVERT() function in SQL Server 2016 SQL Engine
12865966 4501205 Fix: "Non-yielding Scheduler" occurs when you clean up in-memory runtime statistics of Query Store in SQL Server 2016 SQL Engine
12834142 4501741 FIX: URL encoding is incorrect when the Excel workbook name is in Russian language in SSRS 2016 Reporting Services
12823777 4501797 FIX: Data movement to DAG Forwarder does not resume automatically after connection time-out in SQL Server 2016 High Availability
12805639  4502400 FIX: SQL Server 2016 does not perform the requested pre-row assignments when you use MERGE statement that performs assignments of local variables for each row SQL performance
12816125  4502427 FIX: Access violation occurs when you run sys.fn_dump_dblog function in SQL Server 2016 SQL Engine
12572712  4502428 FIX: Assertion error occurs when you run a query to access sys.dm_db_xtp_checkpoint_files in SQL Server 2016 In-Memory OLTP

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.