KB5048033: Cumulative Update 16 for SQL Server 2022

Improvements and fixes included in this update

3426244:Fixes an issue in which Data Analysis Expressions (DAX) queries that use SUMMARIZECOLUMNS and ROLLUPGROUP with multidimensional models might produce incorrect results when running multiple queries that have different sub-selects without clearing the cache, which causes inaccurate totals starting from the second query.

3518505: Fixes an issue in which the Data Quality Services (DQS) format is invalid when exporting cleaned data to SQL Server.

3518497:Fixes an issue in which the menu for editing model permissions appears in the wrong location on some system versions (for example, Windows Server 2019).

3586315:FIX: Database is suspended incorrectly when you run ALTER SERVER CONFIGURATION (KB5048510)

2331381: Fixes an issue that causes the BACKUP SERVER WITH METADATA_ONLY snapshot command to fail with the following errors when the SQL Server instance has more than 64 databases:

Msg 3088, Level 16, State 1, Line <linenumber>
Server <servername> with dbid <databaseid> failed to resume in session <sessionid>.
Msg 925, Level 19, State 1, Line <linenumber>
Maximum number of databases used for each query has been exceeded. The maximum allowed is 64.
Msg 0, Level 20, State 0, Line <linenumber>
A severe error occurred on the current command. The results, if any, should be discarded.

3567000:Fixes a deadlock issue that you might encounter when performing a Transact-SQL snapshot backup using the METADATA_ONLY option under heavy concurrent OLTP workloads, which causes an eventual time-out of the backup with the following errors:
Error: 3041, Severity: 16, State: 1.
BACKUP failed to complete the command BACKUP DATABASE <databasename>. Check the backup application log for detailed messages.
<datetime> ERROR: [PID:<pid>:Backup:<backupid>] Snapshot failed with message 'Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.'.

3418488 :Fixes a patching error that you encounter in secondary replicas of an availability group with databases that have SQL replication, change data capture (CDC), or SQL Server Integration Services database (SSISDB) enabled. For more information, see known issue of SQL Server 2022 CU15 or known issue one of SQL Server 2022 CU14.

3487067: Fixes an issue that causes database corruption if a system failure with alternatewritethrough mode occurs.

3435174:
Fixes incorrect results that you might encounter when you use the contained availability group (AG) and remove plans for a specific object by altering it from either a contained AG or non-contained AG connection. When you make changes from a contained AG or non-contained AG connection, the other connection continues to use the old plan for the altered object until it's manually removed from the plan cache.

2696108 : Removes unnecessary log messages written to the SQL Server error log by the sys.sp_flush_ct_internal_table_on_demand stored procedure.

3419788 :Allows you to disable OLE DB streaming by passing -UseOledbStreaming 0 for the Replication Distribution Agent to avoid the error mentioned in Error message when you run the Distribution Agent in SQL Server.

3459385:Fixes an issue in which the full-text auto crawl monitor is aborted when you use full-text search.

3461615: Fixes an issue in which fdhost frequently restarts due to out-of-memory (OOM) of fdhost when there are too many outstanding global batches from SQL Server in the cloud.

3495266: Fixes an issue in which the SQL Server error log might include invalid characters for SQL Server Agent login attempts when the Agent runs a job on a scheduler configured to run automatically once the Agent starts.

3530163: Fixes an issue in which upgrading from SQL Server 2017 or SQL Server 2019 to SQL Server 2022 is blocked during the database model_msdb upgrade phase. The following message appears in the SQL Server error log:
<datetime> Database 'model_msdb' running the upgrade step from version <versionnumber> to version 957.
Additionally, you might see the following error message when trying to log in:
<datetime> Logon Error: 18401, Severity: 14, State: 1.
<datetime> Logon Login failed for user 'UserName'. Reason: Server is in script upgrade mode. Only administrator can connect at this time. [CLIENT: ClientID]

3417400: Fixes a contention issue with high KTM_RECOVERY_MANAGER wait times that you might encounter when running XA distributed transactions.