Skip to the content
The Update Bureau
SQL Server 2025 CU8 SQL Server 2025 CU8 Cumulative update

KB5104822

KB5104822: Cumulative update for SQL Server 2025, CU branch, August 2026. Database recovery queries can trigger access violations; JSON fixes included

In short

Includes 11 fixes for SQL Server 2025. It also has an open issue where querying requests during database recovery might cause an access violation and dump file.

Does it affect you? Applies to: Instances running SQL Server 2025. The update package covers installed SQL Server components, and the article provides installation guidance for Windows and Linux.

Build
17.0.4075.5
Servicing branch
CU
Restart
Required
Review notes Additional details from the official release notes (3) Read notes
  • What changes The fix is for restores using both Volume Shadow Copy Service (VSS) and WITH MOVE when the server contains hundreds of databases.
  • Known issues Linked server queries using MSDASQL with a provider string fail with error 7416.
  • In detail Linked server queries using MSDASQL with a provider string fail with error 7416.

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

Backup Restore

  • Restoring a database with WITH MOVE no longer takes a long time or times out when the server has hundreds of databases.1
    Fixes the issue with restores that use Volume Shadow Copy Service (VSS).

Maintenance Plan

  • An index rebuild maintenance plan no longer stops responding because of a long-running query.2

Deployment Platform

  • Setup recommends the correct max server memory value for Standard and Standard Developer editions: 256 GB instead of 128 GB.3

Linux

For: Linux SQL Server administrators

  • Changing the collation during initial setup no longer unexpectedly blocks mssql-conf on systems with a high CPU count.4

Programmability

5 items
  • OPENJSON no longer returns unexpected rows when a JSON path contains certain special characters.5
    The affected pattern-matching characters include %, _, [ and ].
  • DBCC CHECKTABLE no longer triggers an assertion and dump file for the specified persisted computed column.6
    The issue occurs with EXTENDED_LOGICAL_CHECKS on a persisted computed column that uses the native json data type.
  • JSON_MODIFY no longer returns errors 13643 and 7102 when appending a value to a native JSON array with 65,535 elements.7
  • JSON_MODIFY no longer returns error 13643, state 101, when a native JSON array with 65,536 or more elements is its value argument.8
  • JSON_MODIFY no longer returns errors 13647 and 13643 when overwriting or deleting a stored native JSON array with 65,536 or more elements.9

Improvement 1 change

Replication

  • sp_adddistributor has a new optional @multi_subnet_failover parameter.10

New feature 1 change

PolyBase

For: Linux SQL Server administrators

  • PolyBase supports encrypted communication between its external service and gRPC clients on Linux.11

Known issues

  1. Open Affects: Organizations and IT administrators

    Linked server queries that use MSDASQL fail with error 7416

    Linked server queries that use the MSDASQL provider and specify a provider string (@provstr) might fail with error 7416, stating that no login mapping exists.12

    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

    Access violation when you query sys.dm_exec_requests during database recovery

    Queries against sys.dm_exec_requests might cause an access violation and dump file while a database is recovering, including during RESTORE, startup recovery, or before an availability group replica finishes coming online.13

    How to apply the workaround SQL Trace Flag

    Enable trace flag 4696, avoid querying sys.dm_exec_requests for databases that are recovering, or uninstall this update. With the trace flag enabled, monitoring queries against sys.dm_exec_requests or sys.sysprocesses on secondary replicas might return errors 976 or 978.13

    Step-by-step workaround instructions
    2 steps
    Show steps Hide steps
    Step-by-step procedure
    1. Enable trace flag 4696, noting that monitoring queries on secondary replicas might return errors 976 or 978.
    2. Alternatively, avoid queries against sys.dm_exec_requests for databases that are recovering, or uninstall the update.
  3. Open Affects: Organizations and IT administrators

    Incorrect behavior of SESSION_CONTEXT in parallel plans

    Queries using SESSION_CONTEXT might return incorrect results or generate access violation dump files when they run in parallel query plans, particularly if the session is reset for reuse.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.

Technical details

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

Data sheet

Released
2026-08-13
Classification
Updates
Type
Cumulative update
Servicing branch
CU
Restart
Required
Replaces
KB5096981, KB5093421, KB5084896, KB5081495
+3 earlier KB5077896, KB5075211, KB5078298
Replaced by
KB5122769
VersionBuildChannel
2025 17.0.4075.5 General availability

Security

No vulnerabilities are listed for this update.

Downloads (Microsoft Update Catalog)

Package 2025
414.8 MB
sqlserver2025-kb5104822-x64.exe Main update · KB5104822 SHA-1: f81441d8…8b9045

Updated components

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

Top changed componentsFiles
SQL Server Engine93
SQL Server Integration Services24
SQL Server Replication12
SQL Server Agent4
SQL Server Machine Learning Services4
SQL Server PolyBase4
SQL Server Full-Text Search2

Sources

Updated
Cited passages from Microsoft's official notes (14)
  1. 1. Fixes an issue in which restoring a database by using Volume Shadow Copy Service (VSS) and WITH MOVE takes a long time or times out if the server contains hundreds of databases. support.microsoft.com
  2. 2. Fixes an issue in which an index rebuild maintenance plan stops responding because of a long-running query. support.microsoft.com
  3. 3. Fixes an issue in which SQL Server Setup recommends a max server memory value of 128 GB instead of 256 GB for Standard and Standard Developer editions. support.microsoft.com
  4. 4. Fixes an issue in which changing the collation during initial setup can block mssql-conf unexpectedly on systems that have a high CPU count. support.microsoft.com
  5. 5. Fixes an issue in which OPENJSON returns unexpected rows when a JSON path contains special pattern-matching characters, including %, _, [, or ]. support.microsoft.com
  6. 6. Fixes an assertion and dump file that occur when DBCC CHECKTABLE runs with EXTENDED_LOGICAL_CHECKS against a persisted computed column that uses the native json data type. support.microsoft.com
  7. 7. Fixes errors 13643 and 7102 that occur when JSON_MODIFY appends a value to a native json array that contains 65,535 elements. support.microsoft.com
  8. 8. Fixes error 13643, state 101, that occurs when JSON_MODIFY receives a native json array that contains 65,536 or more elements as its value argument. support.microsoft.com
  9. 9. Fixes errors 13647 and 13643 that occur when JSON_MODIFY overwrites or deletes a stored native json array that contains 65,536 or more elements. support.microsoft.com
  10. 10. Adds a new optional parameter, @multi_subnet_failover, to sp_adddistributor. support.microsoft.com
  11. 11. Adds encryption support for communication between the PolyBase external service and clients that use gRPC on Linux. support.microsoft.com
  12. 12. 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: support.microsoft.com
  13. 13. Enable trace flag 4696 to opt out of the code change that causes this issue. 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
Checked automatically: 8 of 8 checks passed, 14 quoted passages · compared with Microsoft's page on Oct 16, 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 3/5, clarity 4/5, completeness 4/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