KB5048033: Cumulative update for SQL Server 2022, CU branch, November 2024. Linux database corruption and snapshot backup failures fixed
Includes 16 fixes for SQL Server 2022, including a Linux database corruption issue and snapshot backup failures. Queries using SESSION_CONTEXT in parallel plans might still return incorrect results or cause access violation dumps.
Does it affect you? Applies to: SQL Server 2022 installations. The listed fixes cover Windows, Linux, or both, depending on the component.
For servers on the CU branch: they install cumulative updates, which also bring fixes beyond security. Servers on the GDR branch (security fixes only) get a separate update. Which branch am I on?
What changes
Fixes 14 changes
Analysis Services
-
DAX queries using SUMMARIZECOLUMNS and ROLLUPGROUP with multidimensional models return accurate totals when different sub-selects run without clearing the cache.1
Fixes inaccurate totals starting from the second query in this scenario.
Data Quality Services
- Exporting cleaned data to SQL Server no longer produces an invalid Data Quality Services format.2
Master Data Services
- The menu for editing model permissions appears in the correct location on affected system versions, such as Windows Server 2019.3
Backup Restore
- A database is no longer incorrectly suspended when you run ALTER SERVER CONFIGURATION.4
-
The BACKUP SERVER WITH METADATA_ONLY snapshot command no longer fails on SQL Server instances with more than 64 databases.5
Addresses the maximum-databases-per-query errors that caused the command to fail.
-
Transact-SQL snapshot backups using METADATA_ONLY no longer encounter the described deadlock and eventual timeout under heavy concurrent OLTP workloads.6
Fixes the deadlock that could cause BACKUP DATABASE to time out.
High Availability and Disaster Recovery
- Patching no longer encounters the described error on secondary availability group replicas whose databases have SQL replication or change data capture enabled.7
Linux
For: SQL Server on Linux administrators
- A system failure in alternatewritethrough mode no longer causes database corruption.8
Programmability
-
Connections to a contained availability group no longer leave another connection using an old plan after the object's plan is removed.9
Applies when the object is altered from a contained or non-contained AG connection; the other connection previously kept the old plan until it was manually removed from the plan cache.
Search
SQL Agent
-
The SQL Server error log no longer records invalid characters for Agent login attempts in the described job-scheduler scenario.12
Applies when the Agent runs a job on a scheduler configured to run automatically once the Agent starts.
SQL Server Engine
For: SQL Server administrators upgrading to SQL Server 2022
-
Upgrading from SQL Server 2017 or SQL Server 2019 to SQL Server 2022 is no longer blocked during the model_msdb database upgrade phase.13
Addresses the upgrade step to version 957 and the related script upgrade mode login error 18401.
Transaction Services
For: SQL Server administrators running XA distributed transactions
- High KTM_RECOVERY_MANAGER wait-time contention when running XA distributed transactions is addressed. Trace flag 8531 must be enabled as a startup trace flag.14
Improvement 1 change
Replication
For: SQL Server replication administrators
-
You can disable OLE DB streaming for the Replication Distribution Agent to avoid the referenced error.15
Pass -UseOledbStreaming 0 to the Replication Distribution Agent.
Removal 1 change
Replication
- Unnecessary log messages from the sys.sp_flush_ct_internal_table_on_demand stored procedure are no longer written to the SQL Server error log.16
Known issues
-
Incorrect behavior of SESSION_CONTEXT in parallel plans
Queries using the built-in SESSION_CONTEXT function might return incorrect results or trigger access violation dump files when run in parallel query plans, particularly if the session is reset for reuse.17
Workaround status No workaround yetMicrosoft has not published a manual workaround for this issue yet. Monitor release health until a resolving update is available.
Technical details
Data sheet · Security · Downloads · Components Click to collapse or expand
Data sheet
- Released
- 2024-11-14
- Classification
- Updates
- Type
- Cumulative update
- Servicing branch
- CU
- Restart
- Required
- Replaces
- KB5041321, KB5038325, KB5036432, KB5033663, KB5032679
- Replaced by
- KB5048038
| Version | Build | Channel |
|---|---|---|
| 2022 | 16.0.4165.4 | General availability |
Security
No vulnerabilities are listed for this update.
Downloads (Microsoft Update Catalog)
Sources
Cited passages from Microsoft's official notes (17)
-
1.
Fixes an issue in which Data Analysis Expressions (DAX) queries that use
support.microsoft.comSUMMARIZECOLUMNSandROLLUPGROUPwith 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. -
2.
Fixes an issue in which the Data Quality Services (DQS) format is invalid when exporting cleaned data to SQL Server.
support.microsoft.com -
3.
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).
support.microsoft.com -
4.
[FIX: Database is suspended incorrectly when you run ALTER SERVER CONFIGURATION (KB5048510)]
support.microsoft.com -
5.
Fixes an issue that causes the
support.microsoft.comBACKUP SERVER WITH METADATA_ONLYsnapshot command to fail with the following errors when the SQL Server instance has more than 64 databases: -
6.
Fixes a deadlock issue that you might encounter when performing a Transact-SQL snapshot backup using the
support.microsoft.comMETADATA_ONLYoption under heavy concurrent OLTP workloads, which causes an eventual time-out of the backup -
7.
Fixes a patching error that you encounter in secondary replicas of an availability group with databases that have SQL replication or change data capture (CDC) enabled.
support.microsoft.com -
8.
Fixes an issue that causes database corruption if a system failure with
support.microsoft.comalternatewritethroughmode occurs. -
9.
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.
support.microsoft.com -
10.
Fixes an issue in which the full-text auto crawl monitor is aborted when you use full-text search.
support.microsoft.com -
11.
Fixes an issue in which
support.microsoft.comfdhostfrequently restarts due to out-of-memory (OOM) offdhostwhen there are too many outstanding global batches from SQL Server in the cloud. -
12.
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.
support.microsoft.com -
13.
Fixes an issue in which upgrading from SQL Server 2017 or SQL Server 2019 to SQL Server 2022 is blocked during the database
support.microsoft.commodel_msdbupgrade phase. -
14.
Fixes a contention issue with high
support.microsoft.comKTM_RECOVERY_MANAGERwait times that you might encounter when running XA distributed transactions. Note: You need to turn on trace flag 8531 as a startup trace flag. -
15.
Allows you to disable [OLE DB streaming] by passing -UseOledbStreaming 0 for the Replication Distribution Agent to avoid the error
support.microsoft.com -
16.
Removes unnecessary log messages written to the SQL Server error log by the
support.microsoft.comsys.sp_flush_ct_internal_table_on_demandstored procedure. -
17.
Queries that use the built-in
support.microsoft.comSESSION_CONTEXTfunction might return incorrect results or trigger access violation (AV) dump files when run in parallel query plans.
Checked automatically: 8 of 8 checks passed, 17 quoted passages · compared with Microsoft's page on Oct 20, 2026
- Quotes found in the official pages: passed
- Numbers found in the sources: passed
- Vulnerabilities from the dossier only: passed
- Links to allowed domains only: passed
- Every official change covered: passed
- Readable plain text: passed
- Changes confirmed by the file list: passed
- Sources agree: passed
A second AI read the text against the sources: correctness 5/5, clarity 4/5, completeness 5/5. How we work
Published by The Update Bureau. Written with AI from Microsoft's own documents, checked by rules and a second AI. How we work · Report a mistake