KB5017593 - Cumulative Update 18 for SQL Server 2019
Release Date:
28/09/2022
Version:
15.0.4261.1
Summary
This article describes Cumulative Update package 18 (CU18) for Microsoft SQL Server 2019. This update contains 21 fixes that were issued after the release of SQL Server 2019 Cumulative Update 17, and it updates components in the following builds:
-
SQL Server - Product version: 15.0.4261.1, file version: 2019.150.4261.1
-
Analysis Services - Product version: 15.0.35.33, file version: 2018.150.35.33
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 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_NNNNNNNN" 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 |
Platform |
||
|---|---|---|---|---|---|---|
|
The assertion "Status.Prepared" can occur when you perform a cross-database transaction that involves a memory-optimized table. |
In-Memory OLTP |
Windows |
||||
|
Executing multiple SQL Server Agent jobs that use proxy accounts at the same time fails due to BCryptDecrypt issues. Additionally, one of the following errors occurs:
Note You may see this issue when the number of logical processors is high (larger than 32), and the concurrency jobs are also very high. |
Management Tools |
Windows |
||||
|
5017551 |
FIX: Installing SQL Server CUs may trigger IndexOutOfRangeException |
Setup & Install |
Windows |
|||
|
The installation of Microsoft SQL Server 2019 that uses the configuration file ignores the value for the ASCOLLATION parameter and falls back to the system default locale. Note If you don't apply this SQL Server cumulative update, you can use -ASCOLLATION on the command line or UI as a workaround. |
Setup & Install |
Windows |
||||
|
5017718 |
SQL performance |
All |
||||
|
In Microsoft SQL Server 2019 and 2017, an index creation over a persisted computed column and partition function fails. Additionally, the following error 8624 occurs: Internal Query Processor Error: The query processor could not produce a query plan. For more information, contact Customer Support Services. |
SQL performance |
Windows |
||||
|
5018050 |
Improvement: Add new Azure SQL Database service tier options to the Stretch Database feature |
SQL Server Engine |
Windows |
|||
|
5019307 |
FIX: Changes aren't applied to a newly added article in a peer-to-peer topology with a custom port |
SQL Server Engine |
Windows |
|||
|
Fixes a high CPU usage condition that occurs when you enable change tracking on a large number of tables and do automatic or manual cleanup of the change tracking tables. |
SQL Server Engine |
Windows |
||||
|
Transactional replication fails with errors 12300 and 12301 when the replication is enabled on memory optimized tables with computed columns and index on nullable columns respectively. |
SQL Server Engine |
Windows |
||||
|
The READ_COMMITTED_SNAPSHOT isolation level still requests the IS Object lock. Thus, unexpected blocking occurs on the string-type column that has the columnstore index. |
SQL Server Engine |
Windows |
||||
|
The NOLOCK hint still requests the IS Object lock. Thus, unexpected blocking occurs on the string-type column that has the columnstore index. |
SQL Server Engine |
Windows |
||||
|
Managed Backup fails intermittently because of the missing completion signal from the SQL Server Agent that causes backups for databases to stop. |
SQL Server Engine |
Windows |
||||
|
You use the sp_changereplicationserverpasswords stored procedure to change the password of the Microsoft SQL Server login used by replication agents. It fails and causes the following error: Msg 208, Level 16, State 1, Procedure master.sys.sp_MSchangerepltablepasswords, Line <LineNumber> [Batch Start Line 0] Invalid object name 'MSreplservers'. |
SQL Server Engine |
Windows |
||||
|
Access violation dumps are generated sometimes when stored procedures that use the Scalar UDF Inlining feature are used. |
SQL Server Engine |
Windows |
||||
|
High CPU usage occurs when you enable change tracking on a large number of tables and do automatic or manual cleanup of the change tracking tables. |
SQL Server Engine |
Windows |
||||
|
The FILESTREAM feature is not enabled after you restart the operating system because of race conditions from multiple instances of SQL Server. In the error log, you can see the following error message: Error: 5591, Severity: 16, State: 5. FILESTREAM feature is disabled. |
SQL Server Engine |
Windows |
||||
|
Error 9833 "Invalid data for UTF8-encoded characters" can occur in one of the following scenarios:
|
SQL Server Engine |
Windows |
||||
|
The filegroup IDs of the files that belong to the clone database can be incorrect if the source database has gaps in the filegroup IDs due to the removal of files or filegroups. When you try to insert data into the table that belongs to the incorrectly generated clone database, you receive an error message that resembles the following message: Msg 622, Level 16, State 3, Line <LineNumber> The filegroup "<FileGroupName>" has no files assigned to it. Tables, indexes, text columns, ntext columns, and image columns cannot be populated on this filegroup until a file is added. |
SQL Server Engine |
Windows |
||||
|
An application that is running at Read Committed Snapshot Isolation (RCSI) may not see data committed by an XA transaction. |
SQL Server Engine |
All |
||||
|
The Filestream RsFx driver may cause an access violation for IRP_MJ_NETWORK_QUERY_OPEN requests (Windows API GetFileAttributes), which may be triggered by a third-party application like McAfee Application Control on Windows 10. |
SQL Server Engine |
Windows |
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 CU18 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-KB5017593-x64.exe file through the following command:
-
certutil -hashfile SQLServer2019-KB5017593-x64.exe SHA256
|
File name |
SHA256 hash |
|---|---|
|
SQLServer2019-KB5017593-x64.exe |
ED5B8C473A8FDA2EC0FCB6B2F7A861985FBB506D5C704748063A192E1D3E4478 |
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
-
Determine 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.
