Cumulative Update 8 for SQL Server 2016 SP2

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

Note Due to a change made in SQL Server 2016 SP2 CU8 , any single-stripe TDE compressed backups taken on SQL Server 2016 SP2 through SQL Server 2016 SP2 CU4 will not be able to be restored on SQL Server 2016 SP2 CU8 . Downgrade to the previous CU in order to restore these backups. This issue will be fixed in a future CU.

This article describes Cumulative Update package 8 (CU8) (build number: 13.0.5426.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
12414933 4466107 FIX: Encryption scan task triggered upon the startup of a database may be canceled in SQL Server 2016 SQL Engine
12519852 4469600 FIX: Peer-to-peer replication fails in SQL Server 2016 if the host name is not uppercase SQL Engine
12917911 4502658 FIX: "No valid credentials provided" occurs after you restart PolyBase in SQL Server 2016 and 2017 SQL Engine
12975677 4503385 FIX: DAX query requires more than 200 times of memory than the size of the database in SQL Server 2016 and 2017 multidimensional model database Analysis Services
12737583 4503417 FIX: Assertion dump occurs when you select a view on a linked server in SQL Server 2016 and 2017 SQL Engine
12928930 4504511 Improvement: Allow altering external data source in APS in SQL Server 2016 SQL Engine
12949750 4506023 FIX: Geocentric Datum of Australia 2020 is added to SQL Server 2016 SQL Engine
12964579 4506912 FIX: Concurrent Inserts into a CCI can cause deadlock under memory pressure in SQL Server 2016 SQL Engine
13010511 4508472 FIX: Intermittent "row not found" error at Azure SQL DB Subscriber caused by duplication of BEGIN TRAN statements SQL Engine
12991696 4508621 FIX: Data processing is much slower in SSAS 2016 SP2 than in SSAS 2016 SP1 Analysis Services
13017913 4510934 FIX: Prolonged non-transactional usage of FileTable without instance restart may cause non-yielding scheduler error or server crash in SQL Server 2014, 2016 and 2017 SQL Engine
12883565 4511593 FIX: DBCC SHOW_STATISTICS permission check fails with an AV error in SQL Server 2016 and 2017 SQL performance
12912746 4511715 FIX: Filled transaction log causes outages when you run Query Store in SQL Server 2016 and 2017 SQL Engine
12969908 4511751 FIX: Access violation error occurs when SQL Server 2016 uses hash join, hash aggregate, sort or window function in batch-mode plan in the deadlock monitor SQL Engine
12918636 4511816 FIX: Access violation occurs when you enable TF 3924 to clean orphaned DTC transactions in SQL Server 2016 SQL Engine
12987669 4511834 FIX: Memory dumps generate when access violation occurs in SQL Server 2016 High Availability
12680774 4511868 FIX: Error 409 occurs when you back up databases by using BackuptoURL SQL Engine
13049762 4512016 FIX: Syscommittab cleanup causes a lock escalation that will block the syscommittab flush in SQL Server 2016 SQL Engine
12963177 4512130 FIX: Data masking may not be applied when you use PIVOT or UNPIVOT function on masked column in SQL Server 2016 and 2017 SQL security
12929260 4512151 FIX: Access Violation occurs when you use LOG function with a remote query in SQL Server 2016 or 2017 SQL Engine
13044398 4512558 FIX: Assertion error occurs when SQL Server 2016 uses hash join, hash aggregate, sort or window function in batch-mode plan SQL Engine
12933051 4512567 FIX: "Non-yielding Scheduler" occurs when you run queries with batch-mode hash join and/or sort in SQL Server 2016 SQL Engine
13031076 4512821 FIX: Multidimensional mode randomly crashes and an access violation occurs in SQL Server 2016 Analysis Services
12930344 4512956 FIX: Querying sys.tables returns temporary tables created by concurrent users starting from SQL Server 2012 SQL Engine
12970135 4513097 FIX: Restore or RESTORE VERIFYONLY of a TDE-compressed backup fails in SQL Server 2016 and 2017 SQL Engine
13011771 4513099 FIX: Azure storage I/O subsystem may not reset transfer details for a failed I/O resulting in backup errors SQL Engine
12740272 4513236 FIX: Internal thread deadlock occurs on secondary replica of availability group in SQL Server 2016 SP2 and 2017 High Availability
13015911 4513238 FIX: Error 9003 occurs when you back up a database on a secondary replica in Microsoft SQL Server 2016 SQL Engine
12931722 4519682 FIX: Azure Site Recovery and other VSS jobs may report failures on servers hosting SQL Server 2016 instances 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.