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

KB5037331

KB5037331: Cumulative update for SQL Server 2019, CU branch, June 2024. Thirteen fixes include availability group and logging changes

In short

Includes 13 fixes for SQL Server 2019. It also leaves an open issue where SESSION_CONTEXT queries in parallel plans might return incorrect results or cause access violations.

Does it affect you? Applies to: SQL Server 2019 instances. The update package applies to installed SQL Server 2019 components and supports all supported languages.

Build
15.0.4375.4
Servicing branch
CU
Restart
Required
Review notes Additional details from the official release notes (1) Read note
  • Known issues With CU27, setup can initially fail for an availability-group database with replication or CDC enabled, then the upgrade scripts finish after SQL Server starts again outside single-user mode. The page identifies CU29 as the update that fixes this issue.

The official sources are linked at the end of the page.

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

Master Data Services

  • Using a domain account on a computer that is not a domain controller no longer causes the “Network path not found” error.1
    Fixes bug reference 3099327.

Management Services

  • Maintenance plan logs no longer show garbled characters in messages containing non-ASCII characters.2
    Fixes bug reference 3110965.

High Availability and Disaster Recovery

4 items
  • A remote secondary replica no longer stays in “Not Synchronizing” for several minutes after successive failovers between local replicas in the described multi-subnet, multi-region cloud configuration.3
    Applies to configurations with two or more local replicas and one or more remote replicas. Fixes bug reference 2897797.
  • Secondary databases in an availability group might fail to come online intermittently.4
    Fixes bug reference 2994446. The issue can produce startup error 3602.
  • A read-scale availability group without a cluster configuration no longer triggers the described assertion failure.5
    Fixes bug reference 3018480, an assertion at HadrArProxy.cpp:4314.
  • FILESTREAM transactions in an Always On availability group no longer trigger the described assertion dump.6
    Fixes bug reference 3088136.

Linux

For: SQL Server administrators using Linux

  • SQL Server memory use no longer exceeds the configured memory limit in the described issue.7
    Fixes bug reference 3207518, involving memory.memorylimitmb.

Programmability

  • The described assertion failure no longer occurs when UTF-8 collations are used with WITH RESULT SETS.8
    Fixes bug reference 2955030 in CVariableInfo::PviRelease.

Replication

2 items
  • Change tracking cleanup no longer repeatedly consumes CPU when change tracking is disabled on all databases.9
    Fixes bug reference 2962248. If rows remain in sys.syscommittab or dbo.MSchange_tracking_history on databases where change tracking is disabled, re-enable and then disable change tracking on those databases to clean the tracking data.
  • Running sys.sp_flush_CT_internal_table_on_demand on a case-sensitive instance no longer produces the described “Must declare the scalar variable” error.10
    Fixes bug reference 3015695.

Transaction Services

  • The described dump issue in parallel redo no longer occurs.11
    Fixes bug reference 3065392 in sqlmin.dll!ParallelRedoManager::ReleaseDelayedTran.

Improvement 1 change

High Availability and Disaster Recovery

  • The cluster log report includes performance monitor counters when a health check timeout is reported.12
    Adds counters to the cluster log report. Bug reference 3157054.

New feature 1 change

SQL OS

  • A warning is added to the error log when high I/O latencies are detected in Bufferpool Lazy Writer.13
    The message is WARNING Long asynchronous API Call: The scheduling fairness of scheduler can be impacted by an asynchronous API invocation unexpectedly exceeding xxx ms. Bug reference 2901635. The warning can appear thousands of times; that issue is fixed in SQL Server 2019 CU28.

Known issues

  1. Open Affects: Organizations and IT administrators

    Incorrect behavior of SESSION_CONTEXT in parallel plans

    Queries using SESSION_CONTEXT in parallel plans might return incorrect results or trigger access violation dump files, particularly if the session is reset for reuse. No resolution or workaround is listed.14

    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. Resolved Affects: Organizations and IT administrators Resolved by KB5037331

    Issue three: Patching error for secondary replicas in an availability group with databases enabled replication or CDC

    When patching an availability group database with replication or CDC enabled, setup can initially fail in single-user mode. After the SQL Server service starts again outside single-user mode, the upgrade scripts finish and patching completes; no user action is required. This issue is resolved by KB5037331.15

    Resolution Fixed in KB5037331

    Install KB5037331 (or a later cumulative update) on affected devices. No manual workaround is required after updating.

  3. Resolved Affects: Organizations and IT administrators Resolved by KB5039747

    Issue one: Excessive logging of asynchronous API call warning in the error log

    The warning about a long asynchronous API call might fill the SQL Server error log with thousands of entries. SQL Server 2019 CU28 fixes this issue.16

    Resolution Fixed in KB5039747

    Install KB5039747 (or a later cumulative update) on affected devices. No manual workaround is required after updating.

  4. Resolved Affects: Organizations and IT administrators Resolved by KB5039747

    Issue four: Possibility of error 1204 due to disabled lock escalation

    Disabled lock escalation can cause error 1204, stating that the SQL Server Database Engine cannot obtain a LOCK resource. SQL Server 2019 CU28 fixes this issue.16

    How to apply the workaround Workaround

    Uninstall CU26.16

Technical details

Data sheet · Security · Downloads · Components Click to collapse or expand

Data sheet

Released
2024-06-13
Classification
Updates
Type
Cumulative update
Servicing branch
CU
Restart
Required
Replaces
KB5035123, KB5033688
Replaced by
KB5040948
VersionBuildChannel
2019 15.0.4375.4 General availability

Security

No vulnerabilities are listed for this update.

Downloads (Microsoft Update Catalog)

Package 2019
878.6 MB
sqlserver2019-kb5037331-x64.exe Main update · KB5037331 SHA-1: 51a38393…7f0181

Sources

Updated
Cited passages from Microsoft's official notes (16)
  1. 1. Fixes an issue that can cause the "Network path not found" error when you use a domain account on a non-domain controller machine. support.microsoft.com
  2. 2. Fixes an issue in which maintenance plan logs might report garbled characters when the message reported involves non-ASCII characters. support.microsoft.com
  3. 3. Fixes an issue in which the remote secondary replica shows Not Synchronizing for several minutes after successive failovers between local replicas. support.microsoft.com
  4. 4. Fixes an issue in which the secondary databases of an availability group might fail to be online intermittently. support.microsoft.com
  5. 5. Fixes an assertion failure (Location: HadrArProxy.cpp:4314; Expression: !CFeatureSwitchesMin::GetCurrentInstance()->FHadrCheckXClusterAgUcsSizeEnabled() || cbBlob < x_cbMsgBodyMax) that you might encounter when you use read-scale availability groups without a cluster configuration. support.microsoft.com
  6. 6. Fixes an assertion dump issue (Location: hadrlogcapture.cpp:<LineNumber>; Expression: m_pFsManager->GetEnqueuedBlockId () < capturedLogBlockId || capturedLogBlockId == m_pDbPartner->GetFirstLogBlockIdToCapture ()) that you encounter when there are FILESTREAM transactions in an Always On availability group (AG). support.microsoft.com
  7. 7. FIX: Memory exceeds the configured limits that are specified by memory.memorylimitmb in SQL Server (KB5042369) support.microsoft.com
  8. 8. Fixes an assertion failure (Location: sosmemobj.cpp:2744; Expression: pvb->FInUse()) in CVariableInfo::PviRelease that you encounter when you use UTF-8 collations and the WITH RESULT SETS clause. support.microsoft.com
  9. 9. Fixes an issue in which change tracking auto cleanup consumes CPU in cycles every 30 minutes even if change tracking isn't enabled on any databases. support.microsoft.com
  10. 10. Fixes the following error that you encounter when running sys.sp_flush_CT_internal_table_on_demand in a SQL Server instance that has the Case-sensitive (_CS) collation option: support.microsoft.com
  11. 11. Fixes a dump issue that you might encounter in sqlmin.dll!ParallelRedoManager::ReleaseDelayedTran. support.microsoft.com
  12. 12. Adds performance monitor counters to the cluster log report when the health check timeout is reported. support.microsoft.com
  13. 13. Adds the following log message when high I/O latencies are detected in Bufferpool Lazy Writer (ntdll!ZwWriteFile system call) due to a performance issue in the underlying storage: support.microsoft.com
  14. 14. 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
  15. 15. At that time, the patch upgrade scripts finish successfully and patching is complete. Once startup completes, the issue is resolved and no user action is required. support.microsoft.com
  16. 16. This issue is fixed in SQL Server 2019 CU28. support.microsoft.com
Checked automatically: 8 of 8 checks passed, 16 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 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