Skip to the content
The Update Bureau

SQL Server 2025 · Release Health

Known issues in SQL Server 2025

Problems Microsoft has confirmed for this version, from its official release health notes. 3 still open or mitigated.

SQL Server: 2025 2022 2019 2017 2016
All products →

Active known issues

Open & Mitigated
3 active issues
  1. Open SQL Server 2022 2025 Affects: Organizations and IT administrators Started with KB5093420 · Jul 16, 2026

    Access violation when you query sys.dm_exec_requests during database recovery

    Queries against sys.dm_exec_requests might cause an access violation and create a dump file while a database is recovering. This can happen during restore, startup recovery, or before an availability group replica comes online.

    How to apply the workaround SQL Trace Flag

    Enable trace flag 4696, avoid queries against recovering databases, or uninstall the update. With the trace flag, monitoring queries on secondary replicas might return errors 976 or 978.

    Step-by-step workaround instructions
    2 steps
    Show steps Hide steps
    Step-by-step procedure
    1. Enable trace flag 4696 to opt out of the code change.
    2. Alternatively, avoid queries against sys.dm_exec_requests for databases that are recovering, or uninstall the update.
  2. Open SQL Server 2016 2017 2019 2022 2025 Affects: Everyone Started with KB5080999 · Mar 12, 2026

    Linked server queries that use MSDASQL fail with error 7416

    Linked-server queries using the MSDASQL provider and a provider string might fail with error 7416, reporting that no login mapping exists. The Database Engine's stricter connection validation can reject certain configurations that worked in earlier builds.

    How to apply the workaround Workaround

    Use the workaround guidance in the linked Microsoft troubleshooting article.

  3. Open SQL Server 2019 2022 2025 Affects: Everyone Started with KB5033688 · Feb 15, 2024

    Incorrect behavior of SESSION_CONTEXT in parallel plans

    Queries using SESSION_CONTEXT might return wrong results or create access violation dump files when they run in parallel query plans, especially if a session is reset for reuse.

    Workaround status No workaround yet

    Microsoft has not published a manual workaround for this issue yet. Defer KB5033688 on affected systems until a fix is released.

No known issue matches these filters.