Skip to the content
The Update Bureau

SQL Server 2016 · Release Health

Known issues in SQL Server 2016

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

SQL Server: 2025 2022 2019 2017 2016
All products →

Active known issues

Open & Mitigated
4 active issues
  1. 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.

  2. Open SQL Server 2016 Affects: Organizations and IT administrators Started with KB5046062 · Oct 8, 2024

    Resolution

    KB5046856 fixes the “unknown token” error in scheduled database jobs.

    Workaround status No workaround yet

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

  3. Open SQL Server 2016 Affects: Organizations and IT administrators Started with KB5046062 · Oct 8, 2024

    Symptoms

    Some scheduled database jobs might show an “unknown token” error after KB5046062.

    Workaround status No workaround yet

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

  4. Open SQL Server 2016 2017 2019 2022 Affects: Organizations and IT administrators Started with KB5042207 · Sep 10, 2024

    CDC capture job might fail if columns are missing in CDC change tables

    On databases using change data capture (CDC), columns with commas in their names might be missing from CDC tracking tables and cause capture-job failures; a comma-containing column in a tracking table might be dropped during a CDC upgrade. Separately, CDC upgrades can fail when tracking-table column names contain other symbols.

    How to apply the workaround SQL Trace Flag

    Before upgrading the GDR build, enable trace flag T15006 and restart the SQL Server service.

    Step-by-step workaround instructions
    3 steps
    Show steps Hide steps
    Step-by-step procedure
    1. In SQL Server Configuration Manager, open the instance properties and go to the Startup Parameters tab.
    2. Add trace flag T15006, select Add and Apply, then restart the SQL Server service.
    3. Perform the GDR upgrade.

No known issue matches these filters.