Cumulative Update 11 for SQL Server 2016 SP2

Se aplica a: SQL Server 2016 DeveloperSQL Server 2016 EnterpriseSQL Server 2016 Enterprise Core

This article describes Cumulative Update package 11 (CU11) (build number: 13.0.5598.27) 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
12519855 4470057 FIX: Error 41168 occurs when you try to alter DAG SEEDING_MODE in SQL Server 2016 and 2017 High Availability
12880798 4500574 FIX: Self-deadlock occurs when transaction auditing is enabled in SQL Server 2016 and 2017 SQL security
13163646 4521599 FIX: Non-yielding scheduler condition occurs if large number of row-column values are processed in row groups in SQL Server 2016 SQL Engine
13180659 4524542 FIX: MDS and/or LocalDB patch installation fails if you patch SQL Server 2016 with a next CU Setup & Install
13211308 4525483 FIX: Exception error 3628 may occur when you execute stored procedure in SQL Server 2016 and 2017 SQL Engine
13108557 4525612 FIX: BorderStyle property of TextBox controls may not be rendered in EXCELOPENXML format in SQL Server 2016 Reporting Services
13218541 4526315 FIX: Database cannot recover and reports error 5243 in SQL Server 2016 and 2017 SQL Engine
13159458 4527229 FIX: UPDATE STATISTICS takes very long time to generate maintenance plan for large databases in SQL Server 2016 and 2017 Management Tools
13178749 4527355 FIX: Synchronized job may fail when the target servers start to synchronize the database in SQL Server 2016 Analysis Services
13219010 4527716 FIX: You may encounter a non-yielding scheduler condition when you run query with parallel batch-mode sort operator in SQL Server 2016 SQL performance
13233701 4528065 FIX: DBCC CHECKDB with EXTENDED_LOGICAL_CHECKS fails on a table in SQL Server 2016 SQL Engine
13229640 4528066 FIX: Unable to restore SQL Server 2012 databases on SQL Server 2016 because of NCCI SQL Engine
13229516 4528067 FIX: Error 8959 may occur on IAM page when you query sys.dm_db_index_physical_stats against partitioned columnstore table after partition switch in SQL Server SQL performance
13207394 4528130 FIX: Access violation occurs when you restore the In-Memory Optimized database in SQL Server 2016 and 2017 In-Memory OLTP
13112345 4528250 FIX: Assertion error occurs when you use IDENT_CURRENT on view that has identity columns in SQL Server 2016 In-Memory OLTP
13215464 4529876 FIX: Memory may not get released when you process partitions with data in SQL Server 2016 Analysis Services
13201027 4529942 FIX: Restore fails when you try to restore compressed TDE backups prior to SQL Server 2016 SP2 CU4 on SQL Server 2016 SP2 CU8 SQL Engine
13180656 4530212 FIX: Access violation occurs when you use sys.dm_os_memory_objects in SQL Server 2016 and 2017 SQL performance
13198715 4530251 FIX: Error 8601 occurs when you run a query with partition function in SQL Server SQL performance
13248516 4530259 FIX: Scripts generated by SSMS collect different wait types after you install SQL Server 2016 SP2 CU10 SQL Engine
13207875 4530443 FIX: Non-yielding scheduler issue occurs in SQL Server 2016 when you run an online build for an index that is not partition-aligned SQL performance
13255946 4530475 FIX: IsError function fails to detect error in Excel XIRR function when MDX query is executed from SSIS 2016 Analysis Services
13261030 4530500 FIX: Assertion dump occurs when sp_cdc_disable_db is executed to disable CDC or when distributed transaction is commited after ROLLBACK SAVEPOINT in SQL Server SQL Engine
13224868 4530720 FIX: "The File location cannot be opened" error occurs when you try to open a FileTable directory in SQL Server SQL Engine
13121512 4531010 FIX: CREATE INDEX with new CE reads the partition table and results in huge row count higher than than the total table row count in SQL Server 2016 SQL performance
13202407 4531027 FIX: Assertion error occurs when you run getHKTable function to get Hekaton database 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.