Skip to the content
The Update Bureau
SQL Server 2022 CU24 SQL Server 2022 CU24 Cumulative update

KB5080999

KB5080999: Cumulative update for SQL Server 2022, CU branch, March 2026. Parallel SESSION_CONTEXT errors and listener warnings remain open

In short

CU24 fixes 14 SQL Server 2022 issues, but parallel SESSION_CONTEXT queries can return wrong results or cause access violations. Availability group listeners might also generate error-log messages.

Does it affect you? Applies to: SQL Server 2022 on Windows and Linux. The package updates the SQL Server components installed on the instance.

Build
16.0.4245.2
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 9 changes

High Availability and Disaster Recovery

3 items
  • Creating or restoring a database through a contained availability group connection works correctly.1
  • A configure-only replica of a contained availability group can connect after a restart.6
    Fixes a startup failure that prevented the configure-only replica from connecting.
  • Using a local monitor server for Log Shipping with a contained availability group works correctly after failover.7

Backup Restore

  • A database operation no longer gets stuck in an infinite loop when a sort buffer needs more pages than the supported limit.2
    Fixes an infinite loop in the in-memory sort buffer calculation when the required page count exceeds supported limits.

Query Processing

  • Query execution no longer breaks when switching between Hekaton and non-Hekaton stacks.3
    Fixes a floating point exception when switching from a Hekaton to a non-Hekaton stack.

Access Methods

  • Sorting a rowset larger than four billion rows no longer fails with an assertion error.4

Replication

For: SQL Server administrators using replication with availability groups

  • The distribution agent uses the availability group listener name in the described case-sensitive configuration.5
    Corrects the agent's choice of name when the distributor is in an availability group using case-sensitive (_CS) collation.

Linux

For: SQL Server administrators on Linux

  • The Linux disk statistics field name is corrected.8
    Corrects ios_in_progess to ios_in_progress in sys.dm_os_linux_disk_stats.

Programmability

  • Altering a disabled DDL trigger no longer causes a memory access violation.9

New features 4 changes

Replication

  • Replication can use a new optional setting for multi-subnet failover.10
    Adds the optional @multi_subnet_failover parameter to sp_adddistributor.

Search

  • Full-text search batches can have a configurable timeout.11
    Adds sp_fulltext_service 'batch_timeout'; specify a value in milliseconds from one minute to one hour. The default is 10 minutes if there are no progress updates.

Linux

2 items

For: SQL Server administrators on Linux

  • The getattribute API supports symbolic links.12
  • A configuration option can allow Bulkadmin operations.13
    Adds a configuration option to add Bulkadmin operations to the allowlist.

Improvement 1 change

Security Infrastructure

  • The check of frequently accessed metadata tables now includes sysowners to address contention.14

Known issues

  1. Open Affects: Organizations and IT administrators

    Linked server queries that use MSDASQL fail with error 7416

    Linked server queries using MSDASQL and specifying a provider string (@provstr) can fail with error 7416, saying no login mapping exists.15

    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.

  2. Open Affects: Organizations and IT administrators

    Incorrect behavior of SESSION_CONTEXT in parallel plans

    Queries using SESSION_CONTEXT might return incorrect results or produce access violation dump files when run in parallel plans, particularly if the session is reset for reuse.16

    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.

  3. Open Affects: Organizations and IT administrators

    Availability group listener error 10013 in error log

    When the SQL Server service starts or an availability group fails over, listener-related errors might appear in the error log. Creating a listener might also produce an error that its TCP port is already in use. The messages do not affect functionality, and listener connections continue to work.17

    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
2026-03-12
Classification
Updates
Type
Cumulative update
Servicing branch
CU
Restart
Required
Replaces
KB5078297, KB5068450, KB5065865, KB5059390
+9 earlier KB5054531, KB5050771, KB5048038, KB5048033, KB5041321, KB5038325, KB5036432, KB5033663, KB5032679
Replaced by
KB5083252
VersionBuildChannel
2022 16.0.4245.2 General availability

Security

No vulnerabilities are listed for this update.

Downloads (Microsoft Update Catalog)

Updated components

196 files changed since the previous update for the same versions.

Top changed componentsFiles
SQL Server Engine30
SQL Server Replication12
SQL Server Integration Services10
SQL Server Agent5
SQL Server Machine Learning Services4
SQL Server Full-Text Search2
SQL Server PolyBase2

Sources

Updated
Cited passages from Microsoft's official notes (17)
  1. 1. Fixes an issue that occurs when creating or restoring a database on a contained availability group connection. learn.microsoft.com
  2. 2. Fixes an issue in the in-memory sort buffer calculation that causes an infinite loop when the required page count exceeds supported limits. learn.microsoft.com
  3. 3. Fixes a floating point exception that occurs when switching from a Hekaton to a non-Hekaton stack. This action causes query execution to break. learn.microsoft.com
  4. 4. Fixes an issue in which a sort operation on a rowset that's larger than four billion rows fails and generates an assertion error. learn.microsoft.com
  5. 5. The distribution agent incorrectly uses the AG primary replica name instead of the AG listener name. learn.microsoft.com
  6. 6. Fixes an issue in which the configure-only replica of a Contained Availability Group cannot be connected after a restart because of a startup failure. learn.microsoft.com
  7. 7. Fixes an issue that occurs when using a local monitor server for Log Shipping and Contained Availability Group after failover. learn.microsoft.com
  8. 8. Fixes a typo in sys.dm_os_linux_disk_stats by correcting ios_in_progess to ios_in_progress. learn.microsoft.com
  9. 9. Fixes an issue in which altering a disabled DDL trigger causes a memory access violation. learn.microsoft.com
  10. 10. Adds a new optional parameter, @multi_subnet_failover, to sp_adddistributor. learn.microsoft.com
  11. 11. Adds a configurable full-text search batch timeout by using sp_fulltext_service 'batch_timeout'. Specify a value between one minute and one hour, in milliseconds. learn.microsoft.com
  12. 12. Adds support for symbolic links in the getattribute API. learn.microsoft.com
  13. 13. Adds a configuration option to add Bulkadmin operations to the allowlist. learn.microsoft.com
  14. 14. Addresses contention on security-related metadata tables by adding sysowners to frequently accessed metadata tables check. learn.microsoft.com
  15. 15. Linked server queries that use the MSDASQL (OLE DB Provider for ODBC Drivers) provider and specify a provider string (@provstr) fail and return the following error message: learn.microsoft.com
  16. 16. 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. learn.microsoft.com
  17. 17. This update also causes SQL Server to try to open a TCP port that's already in use when it starts or when a listener is created. This only results in error messages being logged and doesn't affect functionality. Listener connections continue to work. learn.microsoft.com
Checked automatically: 8 of 8 checks passed, 17 quoted passages · compared with Microsoft's page on Sep 26, 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 4/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