KB5026806 - Cumulative Update 5 for SQL Server 2022
Article
Applies to:
SQL Server 2022 on Windows, SQL Server 2022 on Linux
Release Date: June 15, 2023 Version: 16.0.4045.3
Summary
This article describes Cumulative Update package 5 (CU5) for Microsoft SQL Server 2022. This update contains 32 fixes that were issued after the release of SQL Server 2022 Cumulative Update 4, and it updates components in the following builds:
SQL Server - Product version: 16.0.4045.3, file version: 2022.160.4045.3
There are no known issues in this cumulative update.
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 "#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.
Adds additional enforcement of write operations to the encryption algorithm that's used to encrypt data sources and connection strings in SQL Server Analysis Services (SSAS) models. For more information, see Upgrade encryption.
Fixes an issue where a hierarchy created in Master Data Services (MDS) doesn't expand correctly (on both the Edit Derived Hierarchy page and the Hierarchy page in the Explorer area).
Adds an option for the Master Data Services (MDS) configuration tool to decide whether to enable the PerformanceImprovementEnable performance improvement setting.
Fixes the following error that you may encounter when selecting any cell of a domain-based attribute column that has a different name and display name in a Master Data Services (MDS) entity and then selecting the drop-down arrow:
The current cell column title was not found. If the column title was changed, close the sheet and try again.
Adds the sp_validate_certificate_ca_chain stored procedure for checking the validity of the certificate chain used for certificate-based authentication on endpoints of Service Broker, availability groups, and Managed Instance link.
Fixes an issue where applying the option ONLINE in the ALTER INDEX REBUILD statement is invalid when running the index rebuild task created in an index maintenance plan.
Fixes a performance issue that you may encounter when the String Min/Max for Rowgroup Elimination feature is enabled, and you query a clustered columnstore index (CCI) that's built with the feature disabled. The queries that contain simple string predicates may incorrectly qualify a rowgroup.
- You have an instance of SQL Server that connects to Microsoft Entra ID.
- You enable Transport Layer Security (TLS) encryption on this instance of SQL Server.
In this scenario, you may receive the following error 39011 if you run the sp_execute_external_script query against the instance:
Msg 39011, Level 16, State 7, Line <LineNumber> SQL Server was unable to communicate with the LaunchPad service for request id: <ID>. Please verify the configuration of the service.
Fixes an issue where the following error occurs when you disable the FILESTREAM feature on a SQL Server failover cluster instance (FCI) by using SQL Server Configuration Manager (SSCM):
There was an unknown error applying FILESTREAM settings. Check the parameters are valid. (0x800713d6)
Fixes an issue where messages in the sys.transmission_queue of the initiator database in a SQL Server Service Broker conversation are missing or stuck after a failover of the target database.
Fixes an issue where restoring an In-Memory OLTP database backup that has Transparent data encryption (TDE) enabled fails and returns the following error message:
Error: 33126, Severity: 16, State: 1. Database encryption key is corrupted and cannot be read.
Note: To apply this fix, you need to enable a trace flag (TF) to relax TDE checks for In-Memory tables and disable the TF after the restoration is completed. For more information, contact Microsoft Customer Service and Support.
Fixes an assertion dump issue (Location: "sql\\ntdbms\\hekaton\\engine\\core\\tx.cpp":4753; Expression: 0 == Dependencies.CommitDepCountOut) that causes an availability group failover.
Removes the need for running the sys.sp_xtp_force_gc stored procedure twice to free up allocated and used XTP memory, and running it once is enough. You need at least the ALTER SERVER STATE permission to run this procedure.
Adds support for Azure Data Lake Storage (ADLS) Gen2 as a storage location in CREATE EXTERNAL TABLE AS SELECT (CETAS), which fixes the following error 15883 that you encounter when you try to use them:
Msg 15883, Level 16, State 1, Line <LineNumber> Access check for 'CREATE/WRITE' operation against '<Location>' failed with HRESULT = '0x80070057'.
Fixes an issue where external data sources that use the generic ODBC connector may not work after you install SQL Server 2022 CU2 or later versions. You may encounter the following scenarios:
- When you try to query an external table that was created before you install this fix on a generic ODBC data source, and the CONNECTION_OPTIONS argument uses a DSN parameter without the Driver keyword, you receive the following error message:
Msg 7320, Level 16, State 110, Line <LineNumber> Cannot execute the query "Remote Query" against OLE DB provider "MSOLEDBSQL" for linked server "(null)". Object reference not set to an instance of an object.
- If you try to create a new external table, you receive the following error message:
Msg 110813, Level 16, State 1, Line <LineNumber> Object reference not set to an instance of an object.
Fixes an access violation caused by transient race conditions in certain scenarios when parameter sensitive plan (PSP) optimization has Query Store integration enabled.
Fixes a dump issue where the Cardinality Estimation (CE) feedback validation flag is set on statements that come after the statement analyzed by CE Feedback within a batch.
Fixes an issue where applying an update on a secondary replica or performing an in-place upgrade fails when the distribution database is in an availability group. The following error is returned:
Error: There was an error executing the Replication upgrade scripts. See the SQL Server error log for details.
You can see the following error details in the SQL Server error log:
Executing sp_vupgrade_replication. Could not open distribution database distribution because it is offline or being recovered. Replication settings and system objects could not be upgraded. Be sure this database is available and run sp_vupgrade_replication again.
Fixes an issue that you encounter in the following scenario:
- A SQL Server 2017 instance is configured as the Publisher, and a SQL Server 2022 instance is configured as the Distributor.
- The Publication database is configured as a part of an availability group.
In this configuration, the Log Reader Agent fails together with the following error:
<DateTime> Status: 0, code: 20011, text: 'The process could not execute 'sp_replcmds' on 'publisherserver'. <DateTime> Status: 0, code: 18751, text: 'sp_replcmds procedure was called with the wrong number of parameters.'.
Fixes an issue where high PREEMPTIVE_OS_QUERYREGISTRY waits occur. To apply this fix, you need to turn on trace flag 12502, which is used to disable external authorization policies for on-premises SQL Server instances.
- In the meantime, user B's password is changed in the background.
In this scenario, the following error may occur when you create a database and then try to use it:
Msg 916, Level 14, State 2, Line <LineNumber> The server principal "<LoginName>" is not able to access the database "<DatabaseName>" under the current security context.
Fixes an issue where upgrading to SQL Server 2022 database mirroring fails and returns the following errors:
Error: 37526, Severity: 16, State: 1. A ledger table cannot be created while database mirroring is enabled.
Error: 928, Severity: 20, State: 1. During upgrade, database raised exception 3602, severity 25, state 51, address 00007FFFC67A3614. Use the exception number to determine the cause.
Fixes an issue where the following error occurs when you try to manually enter the product key while configuring SQL Server by using the command /opt/mssql/bin/mssql-conf setup or sudo /opt/mssql/bin/sqlservr --pid XXXXX-XXXXX-XXXXX-XXXXX-XXXXX:
The provided PID [XXXXX-XXXXX-XXXXX-XXXXX-XXXXX] is invalid.The PID must be in the form #####-#####-#####-#####-##### where '#' is a number or letter.
Fixes a non-yielding dump issue that you encounter when creating an Extended Events (XEvents) session that captures the sql_text field and has several kilobytes of T-SQL queries.
After applying this update, master databases that are part of contained availability groups will no longer incorrectly report errors when DBCC CHECKDB is being run against them outside of the contained context.
SQL Server Engine
Storage Management
All
How to obtain or download this or the latest cumulative update package
How to obtain or download the latest cumulative update package for Windows (recommended)
The following update is available from the Microsoft Download Center:
Microsoft Update Catalog contains this SQL Server 2022 CU and previously released SQL Server 2022 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.
How to obtain or download the latest cumulative update package for Linux
To update SQL Server 2022 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.
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's 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.
To apply this cumulative update package, you must be running SQL Server 2022.
Restart information
You might have to restart the computer after you apply this cumulative update package.
Registry information
To use one of the hotfixes in this package, you don't have to make any changes to the registry.
Important notices
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 don't 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.
Hybrid environment deployment
When you deploy an update to a hybrid environment (such as Always On, replication, cluster, and mirroring), we recommend that you refer to the following articles before you deploy the update:
If you enabled Always On together with the SSISDB catalog, see the information about SSIS with Always On about how to apply an update in these environments.
SQL Server CUs are currently multilingual. Therefore, this CU package isn't specific to one language. It applies to all supported languages.
Components (features) updated
One CU package includes all available updates for all SQL Server 2022 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 reapply this CU to update the new feature to this CU.
Support for this update
If other 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 don't 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
How to uninstall this update on Windows
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 2022.
Press and hold (or right-click) the entry, and then select Uninstall.
How to uninstall this update on Linux
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.
Administer an SQL Server database infrastructure for cloud, on-premises and hybrid relational databases using the Microsoft PaaS relational database offerings.