SQL Server 2016 SP2: Cumulative Update 8 (KB4505830) Now Available

Updated: 23 Feb, 2025 • 0 • min read

Table of Contents

Release Information¶

SQL Server 2016 SP2: Cumulative Update 8 Release Information

Release Date: July 31, 2019
Version: 13.0.5426.0

This article announces the availability of Cumulative Update package 8 (CU8) for Microsoft SQL Server 2016 Service Pack 2 (SP2). This update, identified by build number 13.0.5426.0, includes a collection of fixes that have been released since the initial launch of SQL Server 2016 SP2. It is crucial for users to be aware of the specific details and recommendations provided within this announcement to ensure a smooth and stable SQL Server environment. This update is available for download from the Microsoft Download Center.

Important Note Regarding TDE Compressed Backups¶

A critical compatibility issue has been identified in SQL Server 2016 SP2 CU8 related to Transparent Data Encryption (TDE) compressed backups. Specifically, single-stripe TDE compressed backups taken on SQL Server 2016 SP2 through Cumulative Update 4 (CU4) will not be restorable on SQL Server 2016 SP2 CU8. If you rely on such backups, it is imperative to downgrade to a previous Cumulative Update in order to successfully restore them. Microsoft has acknowledged this issue and has committed to providing a fix in a future Cumulative Update. Therefore, users employing TDE compressed backups should carefully consider this limitation before applying CU8 in production environments.

Overview of Cumulative Update 8 for SQL Server 2016 SP2¶

SQL Server 2016 SP2 Cumulative Update 8 Overview

Cumulative Update 8 (CU8) for SQL Server 2016 SP2 is now accessible, bringing with it a suite of essential fixes and improvements designed to enhance the stability, performance, and security of your SQL Server instances. This update package, build number 13.0.5426.0, encompasses all hotfixes released post-initial SP2 release, ensuring you receive the most up-to-date corrections. By applying CU8, organizations can benefit from resolutions to known issues, contributing to a more robust and reliable database infrastructure. It is highly recommended to review the included fixes to understand the specific enhancements relevant to your SQL Server deployments.

Improvements and Fixes Included in This Update¶

Improvements and Fixes in SQL Server 2016 SP2 CU8

Cumulative Update 8 for SQL Server 2016 SP2 addresses a range of issues across various SQL Server components. These fixes are categorized by functional areas, including Analysis Services, High Availability, SQL Engine, SQL Performance, and SQL Security. Applying this CU is a proactive step towards mitigating potential problems and optimizing your SQL Server environment. The following sections detail the specific fixes included, categorized for clarity and ease of review. Each fix is identified by a bug reference number and a Knowledge Base (KB) article link for further information.

Details of Fixes¶

Analysis Services Fixes¶

Bug Reference 12975677 - FIX: DAX query requires excessive memory in multidimensional model database (KB4503385): This fix resolves an issue where Data Analysis Expressions (DAX) queries were consuming an unexpectedly large amount of memory, up to 200 times the database size, within SQL Server 2016 and 2017 multidimensional models. This inefficiency could lead to performance degradation and potential server instability. By implementing this fix, memory consumption is optimized, ensuring more efficient DAX query processing.
Bug Reference 12991696 - FIX: Slow data processing in SSAS 2016 SP2 compared to SSAS 2016 SP1 (KB4508621): This update addresses a performance regression in SQL Server Analysis Services (SSAS) 2016 SP2 where data processing operations were significantly slower than in SSAS 2016 SP1. This slowdown could impact data refresh times and overall analytical workload performance. The fix restores data processing speeds to levels comparable with SP1, improving efficiency.
Bug Reference 13031076 - FIX: Multidimensional mode crashes with access violation in SQL Server 2016 (KB4512821): A critical stability issue causing random crashes and access violations in SQL Server 2016 multidimensional mode has been resolved. These crashes could lead to service interruptions and data unavailability. The fix enhances the robustness of the multidimensional mode, preventing these unexpected terminations and improving overall system reliability.

High Availability Fixes¶

Bug Reference 12740272 - FIX: Internal thread deadlock on secondary replica in availability group (KB4513236): This fix addresses a deadlock condition occurring on secondary replicas within Always On Availability Groups in SQL Server 2016 SP2 and 2017. These deadlocks could hinder the performance of secondary replicas and potentially impact read-scale workloads. The resolution eliminates the internal thread deadlock, improving the responsiveness and efficiency of secondary replicas.
Bug Reference 12987669 - FIX: Memory dumps generated on access violation in SQL Server 2016 (KB4511834): An issue causing memory dumps to be generated when access violations occurred in SQL Server 2016 has been rectified. While memory dumps are valuable for debugging, frequent generation due to underlying issues can indicate instability. This fix addresses the root cause of the access violations, reducing the incidence of memory dumps and promoting system stability.

SQL Engine Fixes¶

Bug Reference 12928930 - Improvement: Allow altering external data source in APS (KB4504511): This update introduces an improvement to allow the alteration of external data sources within Analytics Platform System (APS) in SQL Server 2016. This enhancement provides greater flexibility in managing and adapting external data connections in APS environments. Users can now modify external data source configurations as needed without significant disruption.
Bug Reference 12414933 - FIX: Encryption scan task cancellation on database startup (KB4466107): A fix is implemented for an issue where encryption scan tasks triggered upon database startup could be unexpectedly canceled in SQL Server 2016. This cancellation could leave databases in an inconsistent encryption state. The fix ensures that encryption scan tasks complete reliably, maintaining the integrity of database encryption processes.
Bug Reference 12519852 - FIX: Peer-to-peer replication failure with non-uppercase host name (KB4469600): Peer-to-peer replication failures in SQL Server 2016 occurring when the host name was not in uppercase have been resolved. This case-sensitivity issue could disrupt replication topologies. The fix eliminates the host name case dependency, ensuring robust peer-to-peer replication regardless of host name casing.
Bug Reference 12680774 - FIX: Error 409 when backing up databases using BackuptoURL (KB4511868): Error 409, encountered during database backups using BackuptoURL, has been addressed. This error could prevent successful backups to Azure Blob Storage or other URL-based destinations. The fix resolves the underlying cause of Error 409, enabling reliable backups to cloud storage.
Bug Reference 12737583 - FIX: Assertion dump when selecting a view on a linked server (KB4503417): This update corrects an issue leading to assertion dumps when selecting a view on a linked server in SQL Server 2016 and 2017. Assertion dumps can indicate internal inconsistencies and potential instability. The fix prevents these dumps, ensuring smoother interactions with linked servers and views.
Bug Reference 12912746 - FIX: Filled transaction log causes outages when running Query Store (KB4511715): Transaction log growth leading to outages when using Query Store in SQL Server 2016 and 2017 has been addressed. Uncontrolled transaction log growth can exhaust disk space and disrupt database operations. The fix optimizes Query Store transaction log management, preventing excessive growth and enhancing system stability.
Bug Reference 12917911 - FIX: “No valid credentials provided” after restarting PolyBase (KB4502658): The “No valid credentials provided” error occurring after restarting PolyBase in SQL Server 2016 and 2017 has been resolved. This error could prevent PolyBase from connecting to external data sources after a restart. The fix ensures that PolyBase retains and correctly utilizes credentials after service restarts, maintaining connectivity.
Bug Reference 12918636 - FIX: Access violation when enabling TF 3924 for orphaned DTC transactions (KB4511816): An access violation encountered when enabling trace flag 3924 to clean orphaned Distributed Transaction Coordinator (DTC) transactions in SQL Server 2016 has been fixed. Access violations can lead to service interruptions. The fix ensures safe and reliable cleanup of orphaned DTC transactions when using trace flag 3924.
Bug Reference 12929260 - FIX: Access Violation with LOG function in remote query (KB4512151): Access Violation errors occurring when using the LOG function with a remote query in SQL Server 2016 or 2017 have been addressed. These errors could disrupt queries involving remote data access and mathematical functions. The fix ensures correct handling of the LOG function in remote query contexts, preventing access violations.
Bug Reference 12930344 - FIX: Querying sys.tables returns temporary tables from concurrent users (KB4512956): An issue where querying sys.tables was incorrectly returning temporary tables created by concurrent users, starting from SQL Server 2012, has been resolved. This behavior could lead to unexpected results and confusion when querying system metadata. The fix ensures that sys.tables accurately reflects only permanent tables, as intended.
Bug Reference 12931722 - FIX: Azure Site Recovery and VSS job failures on servers hosting SQL Server 2016 (KB4519682): Failures reported by Azure Site Recovery and other Volume Shadow Copy Service (VSS) jobs on servers hosting SQL Server 2016 instances have been addressed. These failures could impact disaster recovery and backup operations. The fix enhances VSS integration with SQL Server, ensuring reliable backups and recovery processes.
Bug Reference 12933051 - FIX: “Non-yielding Scheduler” with batch-mode hash join and/or sort (KB4512567): “Non-yielding Scheduler” errors occurring when running queries with batch-mode hash join and/or sort in SQL Server 2016 have been resolved. These errors could lead to query timeouts and performance degradation. The fix optimizes scheduler behavior in batch-mode operations, preventing non-yielding conditions and improving query performance.
Bug Reference 12944542 - FIX: Slow performance due to CMEMTHREAD waiting on temporary table cachestore (KB4578496): Performance slowdowns due to CMEMTHREAD waiting related to temporary table cachestore memory object contention in SQL Server 2016 and 2017 have been addressed. This contention could become a bottleneck under heavy temporary table usage. The fix optimizes temporary table cachestore management, reducing CMEMTHREAD waits and improving performance in scenarios with frequent temporary table operations.
Bug Reference 12949750 - FIX: Geocentric Datum of Australia 2020 added to SQL Server 2016 (KB4506023): The Geocentric Datum of Australia 2020 has been added to SQL Server 2016. This update ensures accurate spatial data handling for Australian geographic locations utilizing the latest geodetic datum. This addition enhances the precision and applicability of SQL Server spatial features for users in Australia.
Bug Reference 12964579 - FIX: Concurrent Inserts into CCI can cause deadlock under memory pressure (KB4506912): Deadlocks occurring during concurrent inserts into a Columnstore index (CCI) under memory pressure in SQL Server 2016 have been resolved. These deadlocks could impede data loading and concurrent write operations. The fix optimizes CCI insert handling under memory pressure, preventing deadlocks and improving concurrency.
Bug Reference 12969908 - FIX: Access violation error in deadlock monitor with batch-mode plan (KB4511751): Access violation errors in the deadlock monitor when SQL Server 2016 uses hash join, hash aggregate, sort, or window function in a batch-mode plan have been fixed. These errors could impact deadlock detection and resolution processes. The fix enhances the stability of the deadlock monitor in batch-mode scenarios, ensuring reliable deadlock handling.
Bug Reference 12970135 - FIX: Restore or RESTORE VERIFYONLY of TDE-compressed backup fails (KB4513097): Failures during restore or RESTORE VERIFYONLY operations of TDE-compressed backups in SQL Server 2016 and 2017 have been addressed. This fix is particularly important in light of the note about TDE compressed backups in CU8. This separate fix likely addresses a different restore issue not related to the CU8 incompatibility. The details of this fix would need to be reviewed in the KB article.
Bug Reference 13010511 - FIX: Intermittent “row not found” error at Azure SQL DB Subscriber due to BEGIN TRAN duplication (KB4508472): Intermittent “row not found” errors at Azure SQL DB Subscribers caused by duplication of BEGIN TRAN statements have been resolved. This replication issue could lead to data inconsistencies and synchronization problems. The fix ensures correct transaction handling in replication scenarios, preventing “row not found” errors.
Bug Reference 13011771 - FIX: Azure storage I/O subsystem may not reset transfer details causing backup errors (KB4513099): An issue where the Azure storage I/O subsystem might not reset transfer details for failed I/O operations, resulting in backup errors, has been fixed. This issue could disrupt backups to Azure storage. The fix ensures proper I/O subsystem behavior, improving the reliability of backups to Azure.
Bug Reference 13015911 - FIX: Error 9003 when backing up database on a secondary replica (KB4513238): Error 9003 encountered when backing up a database on a secondary replica in Microsoft SQL Server 2016 has been resolved. This error could prevent successful backups from secondary replicas. The fix ensures that backups from secondary replicas complete without Error 9003.
Bug Reference 13017913 - FIX: Prolonged FileTable usage without restart may cause non-yielding scheduler error or server crash (KB4510934): Prolonged non-transactional usage of FileTable without instance restart, potentially leading to non-yielding scheduler errors or server crashes in SQL Server 2014, 2016, and 2017, has been addressed. This issue highlights the importance of periodic restarts when heavily utilizing FileTable. The fix mitigates the risk associated with long-running FileTable usage without restarts.
Bug Reference 13044398 - FIX: Assertion error with batch-mode plan (KB4512558): Assertion errors occurring when SQL Server 2016 uses hash join, hash aggregate, sort, or window function in a batch-mode plan have been fixed. These errors, similar to bug 12969908 but potentially distinct in root cause, further enhance batch-mode stability. The fix reduces the likelihood of assertion errors in complex batch-mode query executions.
Bug Reference 13049762 - FIX: Syscommittab cleanup causes lock escalation blocking syscommittab flush (KB4512016): An issue where syscommittab cleanup could cause lock escalation, blocking the syscommittab flush in SQL Server 2016, has been resolved. This blocking could impact transaction commit performance. The fix optimizes syscommittab cleanup operations, preventing lock escalations and improving transaction throughput.

SQL Performance Fixes¶

Bug Reference 12883565 - FIX: DBCC SHOW_STATISTICS permission check fails with AV error (KB4511593): DBCC SHOW_STATISTICS permission checks failing with an Access Violation (AV) error in SQL Server 2016 and 2017 have been fixed. This issue could prevent users with appropriate permissions from viewing statistics. The fix ensures correct permission checking for DBCC SHOW_STATISTICS, allowing authorized users to access statistics information without errors.

SQL Security Fixes¶

Bug Reference 12963177 - FIX: Data masking not applied with PIVOT or UNPIVOT function on masked column (KB4512130): Data masking not being applied when using the PIVOT or UNPIVOT function on a masked column in SQL Server 2016 and 2017 has been addressed. This could lead to unintended disclosure of masked data. The fix ensures that data masking is correctly applied even when using PIVOT or UNPIVOT functions, maintaining data security.

Download Information¶

Download Cumulative Update 8 for SQL Server 2016 SP2

The latest Cumulative Update package for SQL Server 2016 SP2 is available for download from the Microsoft Download Center.

Download the latest cumulative update package for SQL Server 2016 SP2 now

If you encounter any issues accessing the download page, please contact Microsoft Customer Service and Support to obtain the update package.

Understanding Cumulative Updates¶

Understanding SQL Server Cumulative Updates

Cumulative Updates (CUs) are a standard mechanism for delivering hotfixes and updates for SQL Server. Microsoft utilizes CUs to provide a consistent and predictable release cadence for addressing known issues and introducing incremental improvements. For SQL Server 2016 SP2, only the most recent CU is available on the Microsoft Download Center.

Key characteristics of Cumulative Updates include:

Comprehensive Fix Packages: Each new CU incorporates all fixes that were included in previous CUs for the same SQL Server version and Service Pack. This cumulative nature simplifies update management, as applying the latest CU brings you current with all prior fixes.
Proactive Installation Recommendation: Microsoft strongly recommends ongoing, proactive installation of CUs as they become available. This strategy helps maintain a stable and secure SQL Server environment by addressing potential issues before they impact your operations.
Service Pack Level Certification: SQL Server CUs undergo rigorous certification processes, reaching the same quality levels as Service Packs. This certification provides confidence in the stability and reliability of CUs for production deployments.
Historical Support Case Data: Analysis of historical support data reveals that a significant portion of support cases are related to issues already resolved in released CUs. Implementing CUs can proactively prevent many common problems.
Value Beyond Hotfixes: CUs often contain added value beyond just bug fixes. This may include enhancements in supportability, manageability, and overall reliability, contributing to a more robust SQL Server platform.
Pre-Production Testing: Similar to SQL Server Service Packs, it is crucial to thoroughly test CUs in non-production environments before deploying them to production. This testing ensures compatibility and verifies the expected behavior of the update within your specific environment.
Upgrade to Latest Service Pack: Microsoft recommends upgrading your SQL Server installation to the latest SQL Server 2016 service pack to benefit from the most recent features and improvements.

Deployment in Hybrid Environments¶

Hybrid Environment Deployment for SQL Server Updates

When deploying updates in hybrid environments, which include configurations like Always On Availability Groups, replication, clusters, and mirroring, specific considerations are necessary to ensure a smooth and controlled update process. It is highly recommended to consult the following Microsoft articles before applying CU8 in such environments.

Upgrade a failover cluster instance: Provides guidance on updating SQL Server in a failover cluster environment. For scenarios where a rolling update process is not desired, the following steps are suggested:
1. Install the update on the passive node.
2. Install the update on the active node (service restart required).
Upgrade and update of availability group servers that use minimal downtime and data loss: Details the process for updating Always On Availability Group servers while minimizing downtime and data loss. For environments utilizing Always On with the SSISDB catalog, refer to information about SSIS with Always On for specific update application guidance.
How to apply a hotfix for SQL Server in a transactional replication and database mirroring topology: Provides steps for applying hotfixes in replication and database mirroring topologies.
How to apply a hotfix for SQL Server in a replication topology: Specifically addresses hotfix application in replication topologies.
Upgrading Mirrored Instances: Guidance on upgrading SQL Server mirrored instances.
Overview of SQL Server Servicing Installation: Provides a general overview of SQL Server servicing installation processes.

Language Support¶

SQL Server Cumulative Update Language Support

SQL Server Cumulative Updates are multilingual, meaning a single CU package is not language-specific. This Cumulative Update package applies to all supported languages for SQL Server 2016 SP2. Users can deploy this CU regardless of the language version of their SQL Server installation.

Components Updated¶

Components Updated in SQL Server 2016 SP2 CU8

A single Cumulative Update package encompasses updates for all SQL Server 2016 components (features). However, the CU package will only update those components that are currently installed on the specific SQL Server instance you choose to service. If you add a new SQL Server feature (e.g., Analysis Services) to the instance after applying this CU, you must re-apply CU8 to update the newly added feature to the current CU level. This ensures all components are consistently updated.

Support for This Update¶

Support for SQL Server 2016 SP2 Cumulative Update 8

If you encounter any issues beyond the fixes included in this CU, or if you require troubleshooting assistance, you may need to create a separate service request with Microsoft Support. Standard support costs will apply to additional support questions and issues that do not qualify for the specific Cumulative Update package. For a complete listing of Microsoft Customer Service and Support telephone numbers, or to initiate a new service request, please visit the Microsoft support website.

Uninstalling This Update¶

Uninstall SQL Server 2016 SP2 Cumulative Update 8

To uninstall Cumulative Update 8, follow these steps:

Open Control Panel.
Navigate to Programs and Features, and then select View installed updates.
Locate the entry corresponding to this Cumulative Update package under “Microsoft SQL Server 2016”.
Right-click the entry and select Uninstall.
Follow the on-screen prompts to complete the uninstallation process.

Prerequisites¶

Prerequisites for SQL Server 2016 SP2 Cumulative Update 8

To apply Cumulative Update 8 for SQL Server 2016 SP2, your system must be running SQL Server 2016 SP2. Ensure that the base SQL Server 2016 Service Pack 2 is installed prior to attempting to apply this Cumulative Update.

Restart Requirement¶

Restart Requirement for SQL Server 2016 SP2 Cumulative Update 8

You might be required to restart the computer after applying this Cumulative Update package. It is recommended to plan for a potential restart following the update installation to ensure all changes are properly applied.

Registry Information¶

Registry Information for SQL Server 2016 SP2 Cumulative Update 8

Applying this Cumulative Update package does not necessitate any modifications to the Windows Registry. You do not need to make any manual registry changes to utilize the fixes included in this update.

File Information¶

File Information for SQL Server 2016 SP2 Cumulative Update 8

The English version of this Cumulative Update package contains files with the attributes listed in the extensive tables provided in the original article. These tables detail specific file names, versions, sizes, dates, times, and platforms for various SQL Server 2016 components updated in CU8. For detailed file information, please refer to the original source documentation from Microsoft. The timestamps for these files are in Coordinated Universal Time (UTC), and local time conversion will occur when viewing file information in your system.

Do you have any experiences updating to SQL Server 2016 SP2 CU8? Or perhaps questions about the fixes included? Share your comments and thoughts below!

Computacionvinchi