Skip to the content
The Update Bureau
SQL Server 2019 CU29 SQL Server 2019 CU29 Cumulative update

KB5046365

KB5046365: Cumulative update for SQL Server 2019, CU branch, October 2024. 18 fixes included; SESSION_CONTEXT can misbehave in parallel plans

In short

Includes 18 fixes for SQL Server 2019. Queries using SESSION_CONTEXT might return incorrect results or generate access violation dumps in parallel plans.

Does it affect you? Applies to: SQL Server 2019 installations. The update applies to all supported languages and updates only the components already installed on the selected instance.

Build
15.0.4405.4
Servicing branch
CU
Restart
Required

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 13 changes

Analysis Services

For: Windows instances using multidimensional models

  • DAX queries using SUMMARIZECOLUMNS and ROLLUPGROUP with multidimensional models no longer produce inaccurate totals in the described multi-query scenario.1
    Fixes incorrect results when queries use different sub-selects without clearing the cache; the inaccurate totals can begin with the second query.

Master Data Services

For: Windows instances using Master Data Services

  • Domain account authentication in the configuration tool can retry with additional authentication methods if the initial attempts fail.2
    After authentication fails in SAM format and by default, the account validation process retries using UPN format and three separate authentication methods.

Backup Restore

2 items
  • The SQL Server VSS Writer can freeze a database for a VSS-based backup.3
    Fixes a failure to freeze the database during a VSS-based backup.
  • Striped database backups made with VDI tools can restore without the described error 3456.4
    Fixes restore failures for database striped backups using virtual device interface (VDI) tools.

High Availability and Disaster Recovery

3 items
  • Creating a distributed availability group no longer triggers the described assertion failure when the number of availability groups is set to something other than two.5
    Fixes the assertion at ListenerSpec.cpp:480 when creating a distributed availability group (DAG) with a specified group count other than two.
  • A log backup on the primary replica no longer stops responding after the secondary replica restarts when there is no additional workload on the primary database.6
  • A patching error on secondary availability-group replicas is fixed for databases with SQL replication or change data capture enabled.7

Replication

For: Instances with change tracking enabled

  • A checkpoint on a database with change tracking no longer encounters the described duplicate-key error.8
    Fixes error 2601 during a checkpoint operation when SQL Server tries to insert a duplicate key.

Search

For: Instances using full-text search

  • The full-text auto crawl monitor no longer aborts when you use full-text search.9

SQL Agent

For: Windows instances using SQL Server Agent

  • The SQL Server error log no longer includes invalid characters for the described SQL Server Agent login attempts.10
    The issue occurs when the Agent runs a job on a scheduler configured to run automatically once the Agent starts.

Temporal

For: Instances using temporal tables

  • Table and column names from database metadata are quoted correctly in the described temporal-table operations.11
    Fixes quoting when stored procedures that manage temporal tables build internal SQL Server batches.

Transaction Services

2 items
  • Frequent calls to sp_lock from multiple connections no longer cause the described memory leak when trace flag 15915 is enabled.12
    The memory isn't cleaned up until the SQL Server service restarts. The fix requires trace flag 15915 to be enabled.
  • High KTM_RECOVERY_MANAGER wait times during XA distributed transactions are addressed when trace flag 8531 is enabled as a startup trace flag.13
    The fix requires trace flag 8531 as a startup trace flag.

New features 4 changes

Integration Services

For: Windows instances using Integration Services

  • A digitally signed catalog file is added to support catalog signing for specified Attunity CDC assemblies.14
    Adds SQL2019_SSIS.cat under %SystemRoot%\System32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE} to sign the listed Attunity.SqlServer CDC assemblies and their resource assemblies.

Replication

For: Instances using the Replication Distribution Agent

  • You can disable OLE DB streaming for the Replication Distribution Agent to avoid the described error.15
    Pass -UseOledbStreaming 0 to the Replication Distribution Agent to disable OLE DB streaming.

Search

For: Windows instances using full-text indexes

  • Trace flag 7617 is available to skip dropping full-text index fragments marked for deletion during database recovery.16
    Makes trace flag 7617 available for this recovery behavior.

Storage Management

  • Trace flag 6981 is available to handle large objects when rebuilding an index affected by the described assertion issue.17
    After enabling trace flag 6981 and rebuilding the affected index, the assertion dump shouldn't be generated again.

Improvement 1 change

Query Execution

For: Instances using PREDICT

  • PREDICT checks the MODEL parameter to help avoid errors caused by incorrect model input.18
    Adds validation for the MODEL parameter when running PREDICT.

Known issues

  1. Open Affects: Everyone

    Incorrect behavior of SESSION_CONTEXT in parallel plans

    Queries using SESSION_CONTEXT might return incorrect results or trigger access violation dump files in parallel query plans, particularly if the session is reset for reuse.19

    Workaround status No workaround yet

    Microsoft 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-10-31
Classification
Updates
Type
Cumulative update
Servicing branch
CU
Restart
Required
Replaces
KB5039747, KB5037331, KB5035123, KB5033688
Replaced by
KB5046860
VersionBuildChannel
2019 15.0.4405.4 General availability

Security

No vulnerabilities are listed for this update.

Downloads (Microsoft Update Catalog)

Package 2019
882.8 MB
sqlserver2019-kb5046365-x64.exe Main update · KB5046365 SHA-1: a63710b8…990334

Sources

Updated
Cited passages from Microsoft's official notes (19)
  1. 1. Fixes an issue in which Data Analysis Expressions (DAX) queries that use SUMMARIZECOLUMNS and ROLLUPGROUP with multidimensional models might produce incorrect results support.microsoft.com
  2. 2. Fixes a domain account authentication issue in the configuration tool by adding an auto-retry method to the account validation part support.microsoft.com
  3. 3. Fixes an issue in which the SQL Server Volume Shadow Copy Service (VSS) Writer can't freeze the database during a VSS-based backup. support.microsoft.com
  4. 4. Fixes an issue in which database striped backups using virtual device interface (VDI) tools might fail to restore with error 3456. support.microsoft.com
  5. 5. Fixes an assertion failure (Location: ListenerSpec.cpp:480; Expression: totalUsed + cbListenerName <= cbObj) that you encounter when creating a distributed availability group (DAG) support.microsoft.com
  6. 6. Fixes an issue in which a log backup stops responding on the primary replica after the secondary replica restarts if no additional workloads exist on the primary database. support.microsoft.com
  7. 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. 8. Fixes an issue with checkpoint operation in which the following error 2601 occurs when SQL Server tries to perform a checkpoint operation on the database that has change tracking enabled support.microsoft.com
  9. 9. Fixes an issue in which the full-text auto crawl monitor is aborted when you use full-text search. support.microsoft.com
  10. 10. Fixes an issue in which the SQL Server error log might include invalid characters for SQL Server Agent login attempts support.microsoft.com
  11. 11. Fixes an issue in which table and column names that are read from database metadata aren't correctly quoted in some cases support.microsoft.com
  12. 12. Fixes a performance issue that you might encounter only when sp_lock is called frequently from multiple connections, which might cause a memory leak. support.microsoft.com
  13. 13. Fixes a contention issue with high KTM_RECOVERY_MANAGER wait times that you might encounter when running XA distributed transactions. support.microsoft.com
  14. 14. Adds SQL2019\_SSIS.cat, a digitally-signed catalog file in %SystemRoot%\System32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}, to sign support.microsoft.com
  15. 15. Allows you to disable OLE DB streaming by passing -UseOledbStreaming 0 for the Replication Distribution Agent support.microsoft.com
  16. 16. Makes trace flag 7617 available to skip dropping full-text index fragments marked as deletion during a database recovery process. support.microsoft.com
  17. 17. Adds trace flag 6981 to handle large objects (LOBs) when rebuilding the index that has an assertion issue support.microsoft.com
  18. 18. Adds a validation for the MODEL parameter when running PREDICT to avoid errors due to the input of wrong models. support.microsoft.com
  19. 19. Queries that use the built-in SESSION_CONTEXT function might return incorrect results or trigger access violation (AV) dump files when run in parallel query plans. support.microsoft.com
Checked automatically: 8 of 8 checks passed, 19 quoted passages · compared with Microsoft's page on Oct 21, 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