KB5023049 - Cumulative Update 19 for SQL Server 2019
Release Date:
2/16/2023
Version:
15.0.4298.1
Notice
This cumulative update includes Security Update 5021125. For more information, see (KB5021125 - Description of the security update for SQL Server 2019 GDR: February 14, 2023.
Summary
This article describes Cumulative Update package 19 (CU19) for Microsoft SQL Server 2019. This update contains 47 fixes that were issued after the release of SQL Server 2019 Cumulative Update 18, and it updates components in the following builds:
-
SQL Server - Product version: 15.0.4298.1, file version: 2019.150.4298.1
-
Analysis Services - Product version: 15.0.35.35, file version: 2018.150.35.35
Known issues in this update
SQL Server 2019 CU14 introduced a fix to address wrong results in parallel plans returned by built-in SESSION_CONTEXT. However, this fix could cause Access Violation dump files 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. To do this, use 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 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 2022, SQL Server 2019, and SQL Server 2017. Select to download this Excel file now.
Note: Individual entries in the following table can be referenced directly through a bookmark. If you select any bug reference ID in the table, a bookmark tag is added to the URL by using the "#bkmk_NNNNNNN" format. You can then share this URL with others so that they can jump directly 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 |
Component |
Platform |
|
|---|---|---|---|---|---|---|
|
Fixes an issue where any member who has the DQS KB Operator (dqs_kb_operator) role or a higher privilege level role can create or overwrite arbitrary files on the machine hosting SQL Server as the account that runs the SQL Server service (the default account is NT SERVICE\MSSQLSERVER). |
Data Quality Services |
Data Quality Services |
Windows |
|||
|
Fixes a rare issue where memory corruption in the ODBC driver can occur in communications between two SQL Server instances. This issue occurs when the target SQL Server instance uses a down-level version of the Tabular Data Stream (TDS) protocol. An improper version check causes image data types to be decoded improperly on the client-side of the connection. |
SQL Server Connectivity |
SQL Server Connectivity |
Windows |
|||
|
Updates the version of msoledbsql.msi from 18.2.3 to 18.6.5 in SQL Server 2019, which resolves signature issues for custom actions. For more information, see Release notes for the Microsoft OLE DB Driver for SQL Server. |
SQL Server Connectivity |
SQL Server Connectivity |
Windows |
|||
|
Fixes an issue where the sqlcmd utility doesn't honor the sqlcmd command ":!!" when you run operating system (OS) commands. For more information, see sqlcmd Commands. |
SQL Server Client Tools |
Command Line Tools |
Windows |
|||
|
Performance issues and deadlocks occur on SQL Server Agent in the msdb database that has automated backups. In addition, you see the following error messages in the SQL Server Agent log: <DateTime> SQLServer Error: 1205, Transaction (Process ID) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. <DateTime> Failed to retrieve job <JobID> from the server. |
SQL Server Client Tools |
SQL Agent |
All |
|||
|
Fixes an issue with differential backup skipping new Page Free Space (PFS) pages after a data file grows around a PFS boundary (a multiple of 8,088 pages; 64,704 KB), resulting in database corruption and a possible crash dump when this differential backup is restored. |
SQL Server Engine |
Backup Restore |
All |
|||
|
Fixes a non-yielding scheduler condition (Msg 17883) that occurs when backup operations can't properly handle abort signals in some cases while waiting for pending I/O writes. |
SQL Server Engine |
Backup Restore |
All |
|||
|
Fixes an Access Violation issue that occurs when removing the database snapshot files on the readable secondary replica of an Always On availability group that has the buffer pool extension enabled. |
SQL Server Engine |
DB Management |
All |
|||
|
Fixes an assertion failure (Location: schemamgr.cpp:1253; Expression: !regularPVSHobt->m_NeedsRefresh && !longtermPVSHobt->m_NeedsRefresh) that may occur when you run sys.dm_tran_persistent_version_store_stats on the secondary replica of an Always On availability group. |
SQL Server Engine |
High Availability and Disaster Recovery |
All |
|||
|
After you apply this fix, the cluster_nodename returns valid results when you query sys.dm_server_services in SQL Server 2019. |
SQL Server Engine |
High Availability and Disaster Recovery |
All |
|||
|
Fixes a failure of the SQL Server resource DLL (hadrres.dll) to report SQLSTATE when you retrieve the health information from SQL Server and SQLGetData returns SQL_ERROR. |
SQL Server Engine |
High Availability and Disaster Recovery |
Windows |
|||
|
After you apply this fix, the SQL Server performance counter 'Log File(s) Size (KB)' for the SQLServer:Databases object is correctly updated for secondary replicas in an Always On availability group (AG) when there is a log growth. |
SQL Server Engine |
High Availability and Disaster Recovery |
Windows |
|||
|
Fixes an access violation issue that occurs on the secondary replica of an Always On availability group while accessing the empty conversation list. This issue occurs due to a concurrency condition when the system processes the messages like HadrExtendedRecoveryForksMsg or HadrEstablishDB. |
SQL Server Engine |
High Availability and Disaster Recovery |
All |
|||
|
Fixes an assertion failure that occurs in natively compiled modules when the Inner FOR JSON operator is followed by an operator that buffers the corresponding objects, such as another FOR JSON or ORDER BY operator. Additionally, you may see the following assert expression: Location: memilb.cpp:<LineNumber> |
SQL Server Engine |
In-Memory OLTP |
All |
|||
|
Fixes error 41842 that's incorrectly shown even when natively compiled stored procedures or in-memory transactions don't insert many records in a single transaction. Here's the error message: Error 41842: Too many rows inserted or updated in this transaction. You can insert or update at most 4,294,967,294 rows in memory-optimized tables in a single transaction. |
SQL Server Engine |
In-Memory OLTP |
All |
|||
|
After you apply this update, you need at least the control server permission to run the procedure sys.sp_xtp_force_gc. This update changes the implementation of the procedure to a single call for allocated and used bytes to be freed. Before you apply this update, you need to call it twice. For more information, see Gradual increase in XTP memory consumption. |
SQL Server Engine |
In-Memory OLTP |
Windows |
|||
|
This improvement adds Extended Events functionality to enhance the periodic primary replica to secondary replica notification investigation in availability groups for an in-memory database. New events are generated that provide the oldest active transaction and end of log values. This new tracing will help diagnose errors such as the following: <DateTime> Error: 41316, Severity: 23, State: 7. <DateTime> Restore operation failed for database 'DatabaseName' with internal error code '0x84000004'. |
SQL Server Engine |
In-Memory OLTP |
Windows |
|||
|
Fixes an assertion failure (Location: execcoll.cpp:1305; Expression: 'savepointId > HkTxSavePointDefault') that occurs during the savepoint cleanup in a Hekaton transaction. |
SQL Server Engine |
In-Memory OLTP |
All |
|||
|
Fixes error 8992 [Check Catalog Msg 3853, State 1: Attribute (owning_principal_id=ID) of row (principal_id=ID) in sys.database_principals does not have a matching row (principal_id=ID) in sys.database_principals.] generated by DBCC CHECKDB when executed against a database clone of a change data capture (CDC) enabled source database that has system-defined roles owned by CDC users. |
SQL Server Engine |
Metadata |
All |
|||
|
Starting in SQL Server 2019 CU 19, CREATE EXTERNAL DATA SOURCE supports the use of TNS files when connecting to Oracle, by using the CONNECTION_OPTIONS parameter. |
SQL Server Engine |
PolyBase |
All |
|||
|
Adds the NullOnInvalid method for geometry and geography spatial data types to properly handle invalid spatial data. This enables you to have consistent behavior regardless of whether spatial indexes are used in your query plan. |
SQL Server Engine |
Programmability |
All |
|||
|
5017788 |
SQL Server Engine |
Query Execution |
All |
|||
|
4538581 |
SQL Server Engine |
Query Execution |
All |
|||
|
Fixes a failure to automatically resolve an inter-query deadlock that involves parallel resources. Deadlocks are usually resolved automatically by SQL Server but not for specific conditions before you apply this fix. So if you're collecting xml_deadlock_report Extended Events, you will get continuous outputs for it until you manually kill the problem session. |
SQL Server Engine |
Query Execution |
All |
|||
|
Fixes the following stack overflow error that occurs when deeply nesting APPLY operations: Msg 8621, Level 17, State 1, Line <LineNumber> The query processor ran out of stack space during query optimization. Please simplify the query. Note This fix allows the nesting depth of the APPLY operator to be equal to or better than the functionality in SQL Server 2017. |
SQL Server Engine |
Query Execution |
All |
|||
|
Fixes a failure to raise the proper data type overflow error when a comma-separated values (CSV) file has an integer (int) value larger than the maximum value of int and you run SELECT <integer_column_name> FROM OPENROWSET on this CSV file. |
SQL Server Engine |
Query Execution |
All |
|||
|
The fix stops reporting transient error conditions that @@ERROR previously occurred when running queries by using a plan stored in Query Store (QDS). |
SQL Server Engine |
Query Execution |
All |
|||
|
Improvement: Automatically enables the binary large object (BLOB) trace ring buffer feature when a BLOB assertion failure is detected. This improvement helps to better investigate such issues. |
SQL Server Engine |
Query Execution |
All |
|||
|
Fixes a self-deadlock issue where internal update statistic transactions persist locks, which can cause unresolved deadlocks with user queries. The issue occurs because the lock isn't released when the system runs the update query statistics. After you apply this fix, the lock can be released as intended. |
SQL Server Engine |
Query Execution |
All |
|||
|
5022920 |
SQL Server Engine |
Query Optimizer |
All |
|||
|
Fixes an issue where an authenticated attacker could affect SQL Server memory when executing a specially crafted CREATE STATISTICS or UPDATE STATISTICS statement. |
SQL Server Engine |
Query Optimizer |
All |
|||
|
5018231 |
SQL Server Engine |
Replication |
Windows |
|||
|
Fixes an issue where the Distribution Agent returns a general message code 20046 instead of the connection failure message code 20084 when it fails to connect to the Subscriber by using the non-cached connection. These errors are specific to the Replication Distribution Agent. Error message: 20046: The process encountered a general external error. |
SQL Server Engine |
Replication |
All |
|||
|
Consider the following scenario:
In this scenario, the Log Reader Agent reader thread may generate the following assertion dump when processing the log records: * Location: replrowset.cpp:<LineNumber> |
SQL Server Engine |
Replication |
All |
|||
|
Fixes a gradual memory leak in the SQL Server process (the high usage under MEMORYCLERK_SOSNODE) caused by the Log Reader Agent in transactional replication. |
SQL Server Engine |
Replication |
All |
|||
|
Fixes an issue with Change Tracking manual cleanup that caused internal tables to have orphaned records. Previously if the stored procedure experienced a lock timeout on a given table, cleanup wouldn't mark the table for retry and continue cleaning up the next table in the list. After you apply this fix, the table will be marked for retry. |
SQL Server Engine |
Replication |
All |
|||
|
Fixes an issue where the temporary linked server created by the Log Reader Agent isn't always properly dropped when the publisher is in an Always On availability group (AG) and there's a failover at the distributor. After you apply this fix, the linked server is properly removed. |
SQL Server Engine |
Replication |
Windows |
|||
|
Resolves a query performance issue that affects change tracking autocleanup and manual cleanup queries. |
SQL Server Engine |
Replication |
All |
|||
|
Fixes a primary key violation error that's caused by a timing issue in change data capture (CDC) in SQL Server 2019. The CDC capture process may try to insert a duplicate start_lsn value in the cdc.lsn_time_mapping table, and you may see an error message that resembles the following one: Violation of PRIMARY KEY constraint 'lsn_time_mapping_clustered_idx'. Cannot insert duplicate key in object 'cdc.lsn_time_mapping'. The duplicate key value is (Value). Note This fix covers all the causes of this error. For the same issue that occurs in SQL Server 2019 that has a previous cumulative update installed, SQL Server 2017, and SQL Server 2016, see the previous fix KB 4521739. However, the previous fix didn't cover all the cases. |
SQL Server Engine |
Replication |
All |
|||
|
Fixes error 241 that occurs while running the Snapshot Agent, and the system date format was changed to a different format than the one used by SQL Server. Error message: Conversion failed when converting date and/or time from character string. |
SQL Server Engine |
Replication |
All |
|||
|
5023236 |
SQL Server Engine |
Security Infrastructure |
Windows |
|||
|
Fixes spelling issues in Database Engine error messages in SQL Server 2019. |
SQL Server Engine |
SQL Engine |
All |
|||
|
Fixes an access violation exception that occurs in sqlmin.dll!sort_persistresumableprogress when you try to run the CREATE INDEX command that uses the RESUMABLE = ON option. |
SQL Server Engine |
Table Index Partition |
All |
|||
|
Fixes error 692 that occurs when you create a non-clustered index under the following scenario:
Error message: Msg 692, Level 22, State 1, line <LineNumber> Internal error. Buffer provided to write a fixed column value is too large. Run DBCC CHECKDB to check for any corruption. Note Specifying the included columns in the same order as in the clustered index or removing them from the INCLUDE clause can prevent the error. |
SQL Server Engine |
Table Index Partition |
Windows |
|||
|
Lock escalation policy propagation from a user table that has spatial columns to the internal table of related spatial indexes is enabled, which minimizes the chance of deadlocks in the case of highly concurrent data manipulation language (DML) workloads. |
SQL Server Engine |
Table Index Partition |
All |
|||
|
Fixes an assertion issue (Location: tabcreat.cpp:16938; Expression: idIS/8 < sizeof(bmIndexId)) that occurs when you run ALTER TABLE ALTER COLUMN on a table that has many indexes and statistics. |
SQL Server Engine |
Table Index Partition |
Windows |
|||
|
Fixes an issue where schema modification (Sch-M) locks are acquired on foreign key tables when altering columns on the primary tables even if the transaction isn't related to the foreign key column. After you apply this fix, SQL Server only acquires schema stability (Sch-S) locks on foreign key tables. For more information, see Schema locks. |
SQL Server Engine |
Table Index Partition |
All |
How to obtain or download this or the 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 CU19 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-KB5023049-x64.exe file through the following command:
-
certutil -hashfile SQLServer2019-KB5023049-x64.exe SHA256
|
File name |
SHA256 hash |
|---|---|
|
SQLServer2019-KB5023049-x64.exe |
E1E2C36AA7A3D713597BC12E2EEC2FCEBD126DD10BB45AAC2E5474903CD2C61E |
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 Data Quality
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
Need more help?
Want more options?
Explore subscription benefits, browse training courses, learn how to secure your device, and more.
Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.
