Cumulative Update 1 for SQL Server 2016 SP2

Applies to: Microsoft SQL Server 2016Microsoft SQL Server 2016 Business IntelligenceSQL Server 2016 Developer More

Summary


This article describes Cumulative Update package 1 (CU1) (build number: 13.0.5149.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 and all previous CUs can be located and downloaded from the Microsoft Update Catalog. However, Microsoft recommends that you always install the latest cumulative update available.

Hotfixes that are included in this cumulative update package


VSTS bug number KB article number Description Fix area
11983391 4131193 Performance issues occur in the form of PAGELATCH_EX and PAGELATCH_SH waits in TempDB when you use SQL Server 2016 SQL Engine
11983323 4133164 FIX: Error when a SQL Server Agent job executes a PowerShell command to enumerate permissions of the database Management Tools
11516235 4087406 FIX: Error 9002 when there is no sufficient disk space for critical log growth in SQL Server 2014, 2016, and 2017 SQL Engine
11695337 4092554 FIX: "Cannot use SAVE TRANSACTION within a distributed transaction" error when you execute a stored procedure in SQL Server SQL Engine
11983395 4086173 FIX: Access violation occurs when executing a DAX query on a tabular model in SQL Server Analysis Services Analysis Services
11983390 4099472 PFS page round robin algorithm improvement in SQL Server 2016 SQL Engine
11983376 3028216 FIX: A crash occurs when proactive caching is triggered for a dimension in SSAS Analysis Services
11971819 4230516 FIX: A memory assertion failure occurs and the server is unable to make any new connections in SQL Server SQL Engine
11684529 4164562 FIX: Wrong user name appears when two users log on to MDS at different times in SQL Server Data Quality Services (DQS)
11578522 4089718 Improvement: Performance issue when upgrading MDS from SQL Server 2012 to 2016 Data Quality Services (DQS)
11983360 4094858 FIX: "An unexpected error occurred" when you use DAX measures in Power BI table visualizations in SQL Server Analysis Services
11983362 4094706 FIX: One worker thread seems to hang after another worker thread is aborted when you run a parallel query in SQL Server SQL Engine
11983392 4101502 FIX: TDE enabled database backup with compression causes database corruption in SQL Server 2016 SQL Engine
11983382 4230306

FIX: Restore of a TDE compressed backup is unsuccessful when using the VDI client

SQL Engine
11983383 4163087 FIX: Performance is slow for an Always On AG when you process a read query in SQL Server SQL Engine
11983373 4162814 FIX: An internal exception access violation occurs and the SSAS server stops responding Analysis Services
11922532 4157948 FIX: Floating point overflow error occurs when you execute a nested natively compiled module that uses EXP functions in SQL Server In-Memory OLTP
11983358 4094893 FIX: Database cannot be dropped after its storage is disconnected and reconnected in SQL Server SQL Engine
11983381 4293839 FIX: TDE database goes offline during log flush operations when connectivity issues cause the EKM provider to become inaccessible in SQL Server SQL security
11983386 4058175 FIX: TDE-enabled backup and restore operations are slow if the encryption key is stored in an EKM provider in SQL Server SQL security
11983369 4134175 FIX: Processing a cube with many partitions generates lots of concurrent data source connections in SSAS Analysis Services
11983357 4091245 FIX: Access violation occurs when you query a table with an integer column in SQL Server 2017 and SQL Server 2016 SQL performance
11983366 4101554 FIX: Parallel redo in a secondary replica of an availability group that contains heap tables generates a runtime assert dump or the SQL Server crashes with an access violation error High Availability
11983379 4131960 FIX: An assertion failure occurs when you execute a nested select query against a columnstore index in SQL Server SQL performance
11983359 4132267 FIX: Deploying a SSAS project in SSDT is frequently unsuccessful in SQL Server Analysis Services in Tabular mode Analysis Services
11057341 4052135 FIX: RESTORE HEADERONLY statement for a TDE compressed backup takes a long time to complete in SQL Server SQL Engine
11750742 4098762 FIX: Hidden parameters are included in reports when the Browser role is used in SSRS 2016 Reporting Services
11983394 4163478 FIX: An access violation occurs when incremental statistics are automatically updated on a table in SQL Server SQL performance

Notes for this update


Hybrid environments deployment

When you deploy an update 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 SP1.

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.