KB5050771 - Cumulative Update 18 for SQL Server 2022

KB5050771 - Cumulative Update 18 for SQL Server 2022

Summary
This article describes Cumulative Update package 18 (CU18) for Microsoft SQL Server 2022. This update contains 11 fixes that were issued after the release of SQL Server 2022 Cumulative Update 17 and it updates components in the following builds:

• SQL Server - Product version: 16.0.4185.3, file version: 2022.160.4185.3
• Analysis Services - Product version: 16.0.43.242, file version: 2022.160.43.242

Known issues in this update

• 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

Bug Fixes:
2998962--Fixes an issue in which a copy-only filegroup backup on an availability group secondary replica fails with the following errors:
Msg 3059, Level 16, State 1, Line <linenumber>
This BACKUP or RESTORE command is not supported on a database mirror or secondary replica.
Msg 3013, Level 16, State 1, Line <linenumber>
BACKUP DATABASE is terminating abnormally.
- 3726420--Makes the contained availability group (AG) available to use resource governor workload group that's defined at the instance level. For more information, see Resource governor.
- 3691969--Fixes a race condition that you encounter during flush operations when configuring control.alternatewritethrough = 1, which causes extended waits for some transactions.
- 3867855--Fixes an issue in which a self-signed certificate created for SQL Server on Linux might include a negative serial number.
- 3791615--Fixes an issue in Database Mail in which the information logged into the sysmail_log system table and sysmail_event_log view in the msdb database might be stored and displayed as "???" (for example, when querying objects in SSMS). This issue might happen when the reported message (typically an error condition) contains non-ASCII characters and is more common on localized versions of SQL Server (for example, Japanese), not specific to the language of the SQL Server instance or its collation.
- 3848607--Fixes an issue in which the sys.computed_columns view doesn't show the proper definition when using external tables with file metadata columns.
- 3802029--Fixes an issue in which the manual change tracking cleanup stored procedure incorrectly sets the invalid cleanup version to negative when the TableName parameter isn't passed.
- 3821559--Fixes an issue in which the second article might not have updates correctly replicated if accelerated database recovery (ADR) is enabled on the database using replication with two articles for a single table.
- 3902839--Fixes incorrect results that you encounter when you create a full-text index for a .docx file that contains a hyperlink at the start of a paragraph but without a trailing whitespace at the end of the previous paragraph, which causes the full-text search to fail to correctly index the contents of the hyperlink.
Note: You need to turn on trace flag 7686.
- 3549792--Fixes an error that you encounter when the 'Erase Phantom System Health Records' step in the SQL Server Agent job syspolicy_purge_history tries to connect to other instances and the account running the service doesn't have permission to connect. The following error occurs in the SQL Server error log:
<datetime> Logon Error: 18456, Severity: 14, State: 5.
<datetime> Logon Login failed for user '<username>'. Reason: Could not find a login matching the name provided. [CLIENT: <ip address="">]
- 3800647--Data Quality Services (DQS) is only supported in SQL Server Enterprise and Developer editions. Before the fix, the operation is completed successfully when you try to install DQS in the Standard or Web edition. Moreover, this DQS will automatically be selected for installation when setting up a Windows Server Failover Cluster. Once installed, this DQS can't be configured. After applying this fix, SQL Server Setup won't allow DQS to be installed in SQL Server Standard or Web edition.

• --Note: This fix applies to new installations only. For more information, see Installing Updates from the Command Prompt.
  </ip></username></datetime></datetime></linenumber></linenumber>