This article describes Cumulative Update package 13 (CU13) (build number: 13.0.5820.21) 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 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 togetrher with the previous CU for the installed version or 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
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
|Bug reference||KB article number||Description||Fix area||Platform|
|13395275||Access violation exception may occur when sp_server_diagnostics is executed||High Availability||Windows|
|13418764||DBCC CHECKDB can incorrectly report corruption on Spatial Index if base table has a column called Id||SQL Engine||Windows|
|13422835||4556096||FIX: SSRS 2016 URLs are case-sensitive after applying Security Update GDRs KB4532097 or KB4535706||Reporting Services||Windows|
|13431656||When SP/CU/GDR are applied on the SQL Server 2016 that has LocalDB installed, it may fail to update LocalDB binaries the first time it is executed. However, the second attempt to apply SP/CU/GDR will successfully update the files||Setup & Install||Windows|
|13433228||Improves speed of memory dump generation (filtered dumps) using Page exclusion bitmap mechanism. The PageExclusionBitmap is turned on by default in SQL Server 2016||SQL Engine||Windows|
|13435878||4551720||FIX: Access violation exception occurs when promoting latches of frequently used database pages in SQL Server 2016 and 2017||SQL Engine||Windows|
|13443327||Access violation exception may occur when you execute queries in read uncommitted mode with high concurrent read or write pattern over XML data types||SQL Engine||Windows|
|13457594||When you concurrently create sub directories in a FileTable directory, a deadlock may occur internally in the SQL Server Engine and all subsequent requests to FileTable directories and files may not respond||SQL Engine||Windows|
|13478331||When a replication error such as deadlock occurs, the id value in the MSRepl_errors table increases a lot than the previous id value while it should only increase by 1||Replication||Windows|
|13482849||When you run some alter commands that include rollback immediate option, the rollback may trigger before the command is processed even if the ALTER itself may fail due to lack of permissions. This hotfix will make sure that the rollback is processed only after the ALTER command completes||SQL Engine||Windows|
|13485749||4511771||FIX: Full-Text search auto crawl stops when Availability Group goes offline in SQL Server 2014 and 2016||SQL Engine||Windows|
|13487253||4563115||FIX: Upgrade script may fail if you use Always On Failover Cluster Instance as a secondary replica in SQL Server 2016||SQL Engine||Windows|
|13488608||DELETE statement return Foreign Key check constraint error as following even when REFERENCE table has no matching rows: |
Msg 547, Level 16, State 0, Line LineNumber
The DELETE statement conflicted with the REFERENCE constraint "FK_<TableName>_<ColumnName>".
The conflict occurred in database "<DatabaseName", table "dbo.<TableName>", column '<ColumnName>'.
The statement has been terminated.
|13490149||This improves MDX query execution performance against a dimension user hierarchy which is a ragged hierarchy (HideMemberIf property set ) and has deep hierarchy level in SSAS Multidimensional instance||Analysis Services||Windows|
|13491308||R Setup components fails to download CAB files when TLS 1.0 is disabled. This update includes a new R Setup version to add support for TLS1.2||Setup & Install||Windows|
|13502076||sys.key_constraints reports duplicate rows for an index if you have an XML component id with an id which is same as the "object_id" of the primary key||SQL Engine||Windows|
|13503406||R Setup components fails to download CAB files when TLS 1.0 is disabled. This update includes a new R Setup version to add support for TLS1.2||Setup & Install||Windows|
When you execute DBCC CHECKTABLE, CHECKFILEGROUP and CHECKDB commands against a database with table that contains Clustered Columnstore Index (CCI) located on a read-only filegroup, then you may receive the following error message: Msg 8921, Level 16, State 1, Line LineNumber
Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.
|13508254||4560183||FIX: Distributed transactions may experience long waits with DTC_STATE wait type in SQL Server 2016||SQL Engine||Windows|
|13517385||Assertion exception or Access Violation occurs when you query sys.dm_db_file_space_usage dmv in SQL Server 2016||SQL Engine||Windows|
|13517428||4561305||FIX: Concurrent inserts against tables with columnstore indexes may cause queries to hang in SQL Server 2016||SQL Engine||Windows|
|13520595||Assertion may occur on the mirror server during redo process in SQL Server 2016. Assertion: File: <FileName>, line = LineNumber Failed Assertion = 'result == LCK_OK'||High Availability||Windows|
|13525856||Access violation exception occurs when a query is executed with recursive CTE whose anchor is Clustered Columnstore Index (CCI) in SQL Server 2016||SQL performance||Windows|
|13530802||Access Violation exception occurs when executing a query that references a non-existing partition function in SQL Server 2016||SQL performance||Windows|
|13525672||4563597||FIX: Assertion dump may occur when Implicit Transactions are enabled in SQL Server 2016 and 2017||SQL Engine||Windows|
SQL Server failed to start when CU4 is uninstalled from SQL Server 2019:
The script level for 'system_xevents_modification.sql' in database 'master' cannot be downgraded from XXXXXXXXX to XXXXXXXXX, which is supported by this server. This usually implies that a future database was attached and the downgrade path is not supported by the current installation. Install a newer version of SQL Server and retry opening the database.
|13458569||Spatial data types (Geometry and Geography) are implemented as CLR data types in SQL Server. When the application domain hosting the spatial data type structures is unloaded, the engine treats this as a schema change to the underlying objects referenced in the cursor. As a result, spatial query may fail with related error message when the schema change is detected||SQL Engine||All|
|13508779||4562173||FIX: Availability Group failover generates lot of dumps as DTC support is toggled between PER_DB and NONE multiple times||High Availability||All|
Notes for this update
Hybrid environments deployment
- SQL Server failover cluster rolling update and service pack process.
Note If you don't want to use the rolling update process, follow these steps to apply an update:
- Install the update on the passive node.
- Install the update on the active node (requires a service restart).
- Upgrade and update of availability group servers that use minimal downtime and data loss.
Note If you enabled AlwaysOn with SSISDB catalog, see the information about SSIS with AlwaysOn for more information about how to apply an update in these environments.
- How to apply a hotfix for SQL Server in a transactional replication and database mirroring topology
- How to apply a hotfix for SQL Server in a replication topology
- How to install service packs and hotfixes on an instance of SQL Server that is configured to use database mirroring
- Overview of SQL Server Servicing Installation
Cumulative update package information
To apply this Cumulative Update package, you must be running SQL Server 2016 SP2.
You may have to restart the computer after you apply this Cumulative Update package.
To use one of the hotfixes in this package, you do not have to make any changes to the registry.
- Announcing updates to the SQL Server Incremental Servicing Model (ISM)
- How to obtain the latest service pack for SQL Server 2016
- The script to determine which version and edition of SQL Server Database Engine is running
- The Incremental Servicing Model for SQL Server to deliver hotfixes for reported problems
- Naming schema for Microsoft SQL Server software update packages
- Description of the standard terminology that is used to describe Microsoft software updates