KB5007182 - Cumulative Update 14 for SQL Server 2019
Release Date:
11/22/2021
Version:
15.0.4188.2
Summary
This article describes Cumulative Update package 14 (CU14) for Microsoft SQL Server 2019. This update contains 32 fixes that are issued after the release of SQL Server 2019 Cumulative Update 13, and updates components to the following builds.
-
SQL Server - Product version: 15.0.4188.2, file version: 2019.150.4188.2
-
Analysis Services - Product version: 15.0.35.19, file version: 2018.150.35.19
Known issues in this update
-
After you install CU 14, a parallel query that runs in batch mode might cause an access violation and create a memory dump file. To mitigate the issue, run the query to have a Degree of Parallelism of 1, or disable batch mode processing by using trace flag 9453.
Note This issue is resolved in CU15. -
SQL Server 2019 CU14 introduced a fix to address wrong results in parallel plans returned by built-in SESSION_CONTEXT. However, this fix could lead to Access Violation dumps while resetting the SESSION for reuse. To mitigate this issue, you can disable the original fix, and disable the parallelism for built-in SESSION_CONTEXT to avoid wrong results by using the following trace flags:
-
11042 - This trace flag disables the parallelism for built-in SESSION_CONTEXT.
-
9432 - This trace flag disables the fix introduced in SQL Server 2019 CU14.
Microsoft is working on a fix for this issue that will be available in a future CU.
-
Improvements and fixes included in this cumulative update
A downloadable Excel workbook that contains a summary list of builds, together with their current support lifecycle, is available. The Excel file also contains detailed fix lists for SQL Server 2019 and SQL Server 2017. Click to download this Excel file now.
Note: Individual entries in the following table can be referenced directly via a bookmark. If you select any bug reference ID in the table, a bookmark tag is added to the URL using this format #bkmk_NNNNNNNN. You can then share this URL to others so they can directly jump to the desired fix in the table.
For more information about the bugs that are fixed and enhancements that are included in this cumulative update, see the following Microsoft Knowledge Base articles.
|
Bug reference |
KB article number |
Description |
Fix area |
Platform |
|---|---|---|---|---|
|
Fixes the issue in SSAS 2017, where msmdsrv.log doesn't work when you customize the values of the configuration settings MaxFileSizeMB and MaxNumberOfLogFiles |
Analysis Services |
Windows |
||
|
Fixes an issue where the DirectQuery query has no table join clause when you have a DirectQuery model with many-to-many relationship defined and run a DAX query. |
Analysis Services |
Windows |
||
|
Fixes the issue in MDS 2017, where the derived hierarchy permissions are lost in the copied version |
Data Quality Services (DQS) |
Windows |
||
|
Fixes the following error that occurs when you restore a database file (.mdf) that is larger than 15 GB on SQL Server 2019 Big Data Cluster (BDC) with high availability (HA) configuration: Msg 42019, Level 16, State 4, Line <LineNum> |
High Availability |
Linux |
||
|
Fixes an assert dump "pwchId && cwchId <= MAX_PATH && cwchId > 0" during Always On availability group (AG) Virtual Device Interface (VDI) seeding. |
High Availability |
Windows |
||
|
Fixes an access violation exception that may occur when sp_server_diagnostics is executed. |
High Availability |
Windows |
||
|
Fixes an issue where Last_sent_time and Last_received_time columns in DMV dm_hadr_database_replica_states does not get updated |
High Availability |
Windows |
||
|
Fixes an issue where you encounter an "ex_terminator - Last chance exception handling" memory dump. The memory dump is associated with a lease timeout while the recovery of an Always On availability groups (AG) database is in progress. |
High Availability |
Windows |
||
|
5008107 |
Improvement: Cardinality estimation in Spatial TVF functions in SQL Server 2019 |
SQL Engine |
All |
|
|
4538688 |
SQL Engine |
All |
||
|
5004936 |
SQL Engine |
All |
||
|
5007794 |
SQL Engine |
All |
||
|
5007719 |
FIX: Creating a resumable clustered index on a table with LOB causes corruption in SQL Server 2019 |
SQL Engine |
All |
|
|
5007744 |
FIX: Add checkpoint handling for the first row in NonOptimizedGetAndInsertRows |
SQL Engine |
All |
|
|
5008114 |
FIX: The built-in SESSION_CONTEXT returns wrong results in parallel plans |
SQL Engine |
All |
|
|
5008184 |
SQL Engine |
All |
||
|
5008296 |
SQL Engine |
Windows |
||
|
Fixes an issue where the CollectPageLatchFields can cause an access violation (AV) under certain timing conditions when the latch_suspend_end XEvent is turned on. The underlying reason is that this method assumes the Buffer is stable under the latch, which isn't true if the Buffer isn't in the Hashtable anymore. This hotfix avoids the AV by checking whether the Buffer is still in the Hashtable before accessing its underlying fields. |
SQL Engine |
All |
||
|
Fixes an Access Violation (AV) at RbpEarlyFilter::TinyBitmapFilterSIMD that occurs when you run queries on CLUSTERED COLUMNSTORE INDEX (CCI) tables. Here is the dump file: Stack Dump being sent to <FilePath> |
SQL Engine |
All |
||
|
Fixes the EXCEPTION_INVALID_CRT_PARAMETER dump that is generated on insert or update of wide replicated table. |
SQL Engine |
Windows |
||
|
Fixes the failed assertion that occurs due to implicit conversion where predicate's precision is greater than the value. Msg 3624, Level 20, State 1, Line <LineNumber> Msg 596, Level 21, State 1, Line <LineNumber> Msg 0, Level 20, State 0, Line <LineNumber> |
SQL Engine |
Windows |
||
|
Fixes the following runtime error that occurs when you build a 32-bit application where Microsoft.SqlServer.Rmo.dll is referenced from C:\Program Files (x86)\Microsoft SQL Server\150\SDK\Assemblies\ but Microsoft.SqlServer.Replication.dll isn’t cached in GAC_32 folder (C:\Windows\Microsoft.NET\assembly\GAC_32) with SQL Server 2019: System.IO.FileNotFoundException HResult=0x80070002 Message= Could not load file or assembly 'Microsoft.SqlServer.Replication, Version=15.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified. |
SQL Engine |
Windows |
||
|
Fixes an issue where SQL Server 2019 stops responding and crashes due to "ex_terminator - Last chance exception handling" when you use SQL Server Service Broker. |
SQL Engine |
Windows |
||
|
Fixes an Access Violation (AV) that can occur when you run dynamic management views (DMVs) queries. |
SQL Engine |
Windows |
||
|
5007842 |
SQL performance |
Windows |
||
|
Fixes an issue where executing a query with BATCH_MODE_ON_ROWSTORE = ON causes the following error and a dump occurs during compilation of the execution plan: Msg 596, Level 21, State 1, Line <LineNumber> Cannot continue the execution because the session is in the kill state. Msg 0, Level 20, State 0, Line <LineNumber> A severe error occurred on the current command. The results, if any, should be discarded. |
SQL performance |
All |
||
|
Fixes a non-yielding scheduler dump in sqldk!SOS_MemoryWorkSpace::Lookup. |
SQL performance |
All |
||
|
Fixes an issue in which the query processor can't produce a query plan if the USE PLAN hint specifies a query plan that has a left outer join and an inner join. |
SQL performance |
Windows |
||
|
Fixes a self-deadlock issue where thread always waits for HASH_TABLE_DELETE (HTDELETE) when you run parallel query in batch mode. |
SQL performance |
Windows |
||
|
Fixes an issue causing the assertion fNoReaderWriterConflict. |
SQL performance |
Windows |
||
|
Fixes an issue where the following warning message occurs during the snapshot creation when you run the DBCC CHECKDB against a database that has a memory optimized filegroup: [WARNING] Unable to create PerfCounter instance for DB xx (xxx): 0x800700b7. |
In-Memory OLTP |
Windows |
||
|
Fixes the issue in SSIS 2017 when Dimension Processing returns the following error message: clsid {ID}" could not be created and error code 0x80070005 "Access is denied.". Make sure that the component is registered correctly. OnError: "Dimension Processing failed validation and returned error code 0x80040005" |
Integration Services |
Windows |
How to obtain or download this or latest cumulative update package
The following update is available from the Microsoft Download Center:
Download the latest cumulative update package for SQL Server 2019 now
Notes:
-
Microsoft Download Center will always present the latest SQL Server 2019 CU release.
-
If the download page does not appear, contact Microsoft Customer Service and Support to obtain the cumulative update package.
The following update is available from the Microsoft Update Catalog:
Download the cumulative update package for SQL Server 2019 CU 14 now
Notes:
-
Microsoft Update Catalog contains this SQL Server 2019 CU and previously released SQL Server 2019 CU releases.
-
This CU is also available through Windows Server Update Services (WSUS).
-
We recommend that you always install the latest cumulative update that is available
To update SQL Server 2019 on Linux to the latest CU, you must first have the Cumulative Update repository configured. Then, update your SQL Server packages by using the appropriate platform-specific update command.
For installation instructions and direct links to the CU package downloads, see the SQL Server 2019 Release Notes.
To upgrade Microsoft SQL Server 2019 Big Data Clusters (BDC) on Linux to the latest CU, see the Big Data Clusters Deployment Guidance.
Starting in SQL Server 2019 CU1, you can perform in-place upgrades for Big Data Clusters from the production supported releases (SQL Server 2019 GDR1). For more information, see How to upgrade SQL Server Big Data Clusters.
For additional information, see the Big Data Clusters release notes.
File information
You can verify the download by computing the hash of the SQLServer2019-KB5007182-x64.exe file via the following command:
certutil -hashfile SQLServer2019-KB5007182-x64.exe SHA256
|
File name |
SHA256 hash |
|---|---|
|
SQLServer2019-KB5007182-x64.exe |
19D2ABA52942A16659C2C7702A22373082CF1129A3F1D45D47B9D4929D1082C9 |
The English version of this package has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
|
x64-based versions SQL Server 2019 Analysis Services
SQL Server 2019 Database Services Common Core
SQL Server 2019 sql_dreplay_client
SQL Server 2019 sql_dreplay_controller
SQL Server 2019 Database Services Core Instance
SQL Server 2019 Database Services Core Shared
SQL Server 2019 sql_extensibility
SQL Server 2019 Full-Text Engine
SQL Server 2019 sql_inst_mr
SQL Server 2019 Integration Services
SQL Server 2019 sql_polybase_core_inst
SQL Server 2019 sql_shared_mr
SQL Server 2019 sql_tools_extensions
|
Notes for this update
To apply this cumulative update package, you must be running SQL Server 2019.
You might 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.
This article also provides the following important information:
Analysis Services CU build version
Beginning in Microsoft SQL Server 2017, the Analysis Services build version number and SQL Server Database Engine build version number do not match. For more information, see Verify Analysis Services cumulative update build version.
Cumulative updates (CU)
-
Each new CU contains all the fixes that were included with the previous CU for the installed version of SQL Server.
-
SQL Server CUs are certified to the same levels as service packs, and should be installed at the same level of confidence.
-
We recommend ongoing, proactive installation of CUs as they become available according to these guidelines:
-
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.
-
-
We recommend that you test SQL Server CUs before you deploy them to production environments.
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:
-
SQL Server failover cluster rolling update and service pack process
Notes: If you do not 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 together 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
SQL Server CUs are currently multilingual. Therefore, this CU package is not specific to one language. It applies to all supported languages.
One CU package includes all available updates for all SQL Server 2019 components (features). However, the cumulative update package updates only those components that are currently installed on the SQL Server instance that you select to be serviced. If a SQL Server feature (for example, Analysis Services) is added to the instance after this CU is applied, you must re-apply this CU to update the new feature to this CU.
If additional issues occur, or if any troubleshooting is required, you might have to create a service request. The usual support costs will apply to additional support questions and to issues that do not qualify for this specific cumulative update package. For a complete list of Microsoft Customer Service and Support telephone numbers, or to create a separate service request, go to the Microsoft support website.
How to uninstall this update
-
In Control Panel, open the Programs and Features item, and then select View installed updates.
-
Locate the entry that corresponds to this cumulative update package under SQL Server 2019.
-
Press and hold (or right-click) the entry, and then select Uninstall.
To uninstall this CU on Linux, you must roll back the package to the previous version. For more information about how to roll back the installation, see Rollback SQL Server.
References
-
Announcing updates to the SQL Server Incremental Servicing Model (ISM)
-
SQL Server Service Packs are discontinued starting from SQL Server 2017
-
Determining which version and edition of SQL Server Database Engine is running
-
Naming schema and Fix area descriptions for SQL Server software update packages
-
Description of the standard terminology that is used to describe Microsoft software updates
