Update CU articles with fix info for previously known issues

Elena068 · Elena068 · commit 39b1e8e9d7ae · 2025-04-03T07:07:05.000Z
diff --git a/support/sql/releases/sqlserver-2019/cumulativeupdate10.md b/support/sql/releases/sqlserver-2019/cumulativeupdate10.md
@@ -32,14 +32,16 @@ SELECT UDF1(UDF2());
 …
 ```
 
-A fix will be provided in a future cumulative update. To mitigate this problem, disable Scalar UDF inlining by using either of the following options:
+To mitigate this problem, disable Scalar UDF inlining by using either of the following options:
 
 - Change the definition of UDF2 by adding `WITH INLINE = OFF` to the definition.
 
 - Disable inlining on the database by using `ALTER DATABASE SCOPED CONFIGURATION SET TSQL_SCALAR_UDF_INLINING = OFF`.
 
 For examples of disabling Scalar UDF inlining, see [Disable Scalar UDF Inlining without changing the compatibility level](/sql/relational-databases/user-defined-functions/scalar-udf-inlining#disable-scalar-udf-inlining-without-changing-the-compatibility-level).
 
+This issue is fixed in [SQL Server 2019 CU11](cumulativeupdate11.md#14066089).
+
 ## Improvements and fixes included in this update
 
 A downloadable Excel workbook that contains a summary list of builds, together with their current support lifecycle, is available. The Excel file also contains detailed fix lists for SQL Server 2019 and SQL Server 2017. [Select to download this Excel file now](https://aka.ms/sqlserverbuilds).
diff --git a/support/sql/releases/sqlserver-2019/cumulativeupdate12.md b/support/sql/releases/sqlserver-2019/cumulativeupdate12.md
@@ -25,8 +25,7 @@ This article describes Cumulative Update package 12 (CU12) for Microsoft SQL Ser
 
 If a database in an Always On availability group has duplicate logical file names, either correct that situation or avoid using the automatic seeding functionality after you install SQL Server 2019 CU12.
 
-> [!NOTE]
-> This issue is resolved in [CU14](cumulativeupdate14.md).
+This issue is fixed in [SQL Server 2019 CU14](cumulativeupdate14.md).
 
 ## Improvements and fixes included in this update
 
diff --git a/support/sql/releases/sqlserver-2019/cumulativeupdate13.md b/support/sql/releases/sqlserver-2019/cumulativeupdate13.md
@@ -25,8 +25,7 @@ This article describes Cumulative Update package 13 (CU13) for Microsoft SQL Ser
 
 If a database in an Always On availability group has duplicate logical file names, either correct that situation or avoid using the automatic seeding functionality after you install SQL Server 2019 CU12.
 
-> [!NOTE]
-> This issue is resolved in [CU14](cumulativeupdate14.md).
+This issue is fixed in [SQL Server 2019 CU14](cumulativeupdate14.md).
 
 ## Improvements and fixes included in this update
 
diff --git a/support/sql/releases/sqlserver-2019/cumulativeupdate14.md b/support/sql/releases/sqlserver-2019/cumulativeupdate14.md
@@ -27,8 +27,7 @@ This article describes Cumulative Update package 14 (CU14) for Microsoft SQL Ser
 
 After you install CU14, a parallel query that runs in batch mode might cause an access violation and create a memory dump file. To mitigate the issue, run the query to have a Degree of Parallelism of **1**, or disable batch mode processing by using [trace flag 9453](/sql/t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql#tf9453).
 
-> [!NOTE]
-> This issue is resolved in [CU15](cumulativeupdate15.md).
+This issue is fixed in [SQL Server 2019 CU15](cumulativeupdate15.md#14488550).
 
 ### Issue two
 
diff --git a/support/sql/releases/sqlserver-2019/cumulativeupdate19.md b/support/sql/releases/sqlserver-2019/cumulativeupdate19.md
@@ -44,6 +44,8 @@ If you try to create a new external table, you receive the following error messa
 
 To work around this issue, you can uninstall this cumulative update or add the `Driver` keyword to the `CONNECTION_OPTIONS` argument. For more information, see [Generic ODBC external data sources may not work after installing Cumulative Update](https://techcommunity.microsoft.com/t5/sql-server-support-blog/generic-odbc-external-data-sources-may-not-work-after-installing/ba-p/3783873).
 
+This issue is fixed in [SQL Server 2019 CU21](cumulativeupdate21.md#2312800).
+
 ## Improvements and fixes included in this update
 
 A downloadable Excel workbook that contains a summary list of builds, together with their current support lifecycle, is available. The Excel file also contains detailed fix lists for SQL Server 2022, SQL Server 2019, and SQL Server 2017. [Select to download this Excel file now](https://aka.ms/sqlserverbuilds).
diff --git a/support/sql/releases/sqlserver-2019/cumulativeupdate20.md b/support/sql/releases/sqlserver-2019/cumulativeupdate20.md
@@ -41,6 +41,8 @@ If you try to create a new external table, you receive the following error messa
 
 To work around this issue, you can uninstall this cumulative update or add the `Driver` keyword to the `CONNECTION_OPTIONS` argument. For more information, see [Generic ODBC external data sources may not work after installing Cumulative Update](https://techcommunity.microsoft.com/t5/sql-server-support-blog/generic-odbc-external-data-sources-may-not-work-after-installing/ba-p/3783873).
 
+This issue is fixed in [SQL Server 2019 CU21](cumulativeupdate21.md#2312800).
+
 ### Issue three
 
 This issue is caused by a change introduced in this cumulative update for the [Managed Instance link](/azure/azure-sql/managed-instance/managed-instance-link-feature-overview) feature. Assume that the databases of an Always On availability group have one of the following conditions:
@@ -70,6 +72,8 @@ If you have applied this cumulative update to one or more secondary replicas and
 > [!NOTE]
 > Trace flag 12324 impacts only the Managed Instance Link feature and is only used to activate the changes in SQL Server 2019 CU20.
 
+This issue is fixed in [SQL Server 2019 CU22](cumulativeupdate22.md#2460204).
+
 ## Improvements and fixes included in this update
 
 A downloadable Excel workbook that contains a summary list of builds, together with their current support lifecycle, is available. The Excel file also contains detailed fix lists for SQL Server 2022, SQL Server 2019, and SQL Server 2017. [Select to download this Excel file now](https://aka.ms/sqlserverbuilds).
diff --git a/support/sql/releases/sqlserver-2019/cumulativeupdate21.md b/support/sql/releases/sqlserver-2019/cumulativeupdate21.md
@@ -56,6 +56,8 @@ If you have applied this cumulative update to one or more secondary replicas and
 > [!NOTE]
 > Trace flag 12324 impacts only the Managed Instance Link feature and is only used to activate the changes in SQL Server 2019 CU20 and CU21.
 
+This issue is fixed in [SQL Server 2019 CU22](cumulativeupdate22.md#2460204).
+
 ## Improvements and fixes included in this update
 
 A downloadable Excel workbook that contains a summary list of builds, together with their current support lifecycle, is available. The Excel file also contains detailed fix lists for SQL Server 2022, SQL Server 2019, and SQL Server 2017. [Select to download this Excel file now](https://aka.ms/sqlserverbuilds).
diff --git a/support/sql/releases/sqlserver-2019/cumulativeupdate24.md b/support/sql/releases/sqlserver-2019/cumulativeupdate24.md
@@ -33,6 +33,8 @@ SQL Server 2019 CU24 introduced [fix 2714260](#2714260), which causes an issue w
 
 Microsoft is working on a fix for this issue and it will be available in a future CU.
 
+This issue is fixed in [SQL Server 2019 CU25](cumulativeupdate25.md#2926845).
+
 ## Improvements and fixes included in this update
 
 A downloadable Excel workbook that contains a summary list of builds, together with their current support lifecycle, is available. The Excel file also contains detailed fix lists for SQL Server 2022, SQL Server 2019, and SQL Server 2017. [Select to download this Excel file now](https://aka.ms/sqlserverbuilds).
diff --git a/support/sql/releases/sqlserver-2019/cumulativeupdate26.md b/support/sql/releases/sqlserver-2019/cumulativeupdate26.md
@@ -31,7 +31,9 @@ This article describes Cumulative Update package 26 (CU26) for Microsoft SQL Ser
 
 SQL Server 2019 CU26 introduced a regression that can disable lock escalation, which causes error 1204 "The instance of the SQL Server Database Engine cannot obtain a LOCK resource at this time."
 
-To work around this issue, you can uninstall the CU26 or install the [CU28](cumulativeupdate28.md).
+To work around this issue, you can uninstall the CU26.
+
+This issue is fixed in [SQL Server 2019 CU28](cumulativeupdate28.md#3282395).
 
 ## Improvements and fixes included in this update
 
diff --git a/support/sql/releases/sqlserver-2019/cumulativeupdate27.md b/support/sql/releases/sqlserver-2019/cumulativeupdate27.md
@@ -27,7 +27,7 @@ This article describes Cumulative Update package 27 (CU27) for Microsoft SQL Ser
 
 The newly-created warning message in issue [2901635](#2901635) might fill up the SQL Server error log with thousands of occurrences. 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." This is due to an incorrect code change during the build process. If you experience this issue and prefer not to uninstall the CU as a solution, contact [Microsoft Support](https://support.microsoft.com/contactus/?ws=support).
 
-Microsoft is working on a fix for this issue and it will be available in a future CU.
+This issue is fixed in [SQL Server 2019 CU28](cumulativeupdate28.md#3312461).
 
 ### Issue two: Access violation when session is reset
 
@@ -41,7 +41,9 @@ Microsoft is working on a fix for this issue and it will be available in a futur
 
 SQL Server 2019 CU26 introduced a regression that can disable lock escalation, which causes error 1204 "The instance of the SQL Server Database Engine cannot obtain a LOCK resource at this time."
 
-To work around this issue, you can uninstall the CU26 or install the [CU28](cumulativeupdate28.md).
+To work around this issue, you can uninstall the CU26.
+
+This issue is fixed in [SQL Server 2019 CU28](cumulativeupdate28.md#3282395).
 
 ## Improvements and fixes included in this update
 
diff --git a/support/sql/releases/sqlserver-2019/cumulativeupdate28.md b/support/sql/releases/sqlserver-2019/cumulativeupdate28.md
@@ -54,7 +54,7 @@ App-consistent recovery point generation failed.
 
 The issue arises from a code change in SQL Server 2019 CU28 that checks if a database is online and ready to be frozen. The current solution is to roll back to SQL Server 2019 CU27 and perform the snapshot backup. For more information about how to roll back the package to a previous version, see [Uninstall a Cumulative Update from SQL Server](/sql/sql-server/install/uninstall-a-cumulative-update-from-sql-server).
 
-This issue is fixed in [SQL Server 2019 CU29](../sqlserver-2019/cumulativeupdate29.md#3459328).
+This issue is fixed in [SQL Server 2019 CU29](cumulativeupdate29.md#3459328).
 
 ## Improvements and fixes included in this update
 
diff --git a/support/sql/releases/sqlserver-2019/cumulativeupdate3.md b/support/sql/releases/sqlserver-2019/cumulativeupdate3.md
@@ -29,7 +29,7 @@ There's a known uninstallation issue that affects this SQL Server 2019 CU3 under
 
 To mitigate this issue, enable Trace Flag - T902 to bring SQL Server online. You don't have to uninstall the program again. To upgrade to a new CU, you must first remove this flag.
 
-SQL Server 2019 CU5 or any later CU release contains the fix.
+This issue is fixed in [SQL Server 2019 CU5](cumulativeupdate5.md#13543133).
 
 ## Improvements and fixes included in this update
 
diff --git a/support/sql/releases/sqlserver-2019/cumulativeupdate31.md b/support/sql/releases/sqlserver-2019/cumulativeupdate31.md
@@ -43,6 +43,8 @@ When the AG is dropped after patching, you'll see the error message in the [SQL
 
 After the patch is installed, the metadata is removed and you must re-create the AG on the patched replica. If the AG replicas have mismatched SQL Server versions (for example, the primary replica is running SQL Server 2019 CU30 and the secondary replica is running SQL Server 2019 CU31), you can't re-create the AG on the replica with the missing metadata (the secondary replica). In order to add the AG again, you must uninstall the patch on the secondary replica first and then add the AG again.
 
+This issue is fixed in [SQL Server 2019 CU32](cumulativeupdate32.md#3907024).
+
 #### Example
 
 You can use steps that are similar to the following ones, but you need to update them for the given environment, including the `CLUSTER_TYPE`. The VM1 in the given example is the primary replica of the AG 'readscaleag' and VM2 is the secondary replica that has the patch applied but already uninstalled. Before running the script, both replicas VM1 and VM2 are running SQL Server 2019 CU30 and the AG metadata is missing on VM2. To run this script, use [SQLCMD mode](/sql/tools/sqlcmd/edit-sqlcmd-scripts-query-editor).
diff --git a/support/sql/releases/sqlserver-2019/cumulativeupdate4.md b/support/sql/releases/sqlserver-2019/cumulativeupdate4.md
@@ -29,7 +29,7 @@ There's a known uninstallation issue that affects this SQL Server 2019 CU4 under
 
 To mitigate this issue, enable Trace Flag - T902 to bring SQL Server online. You don't have to uninstall the program again. To upgrade to a new CU, you must first remove this flag.
 
-SQL Server 2019 CU5 or any later CU release contains the fix.
+This issue is fixed in [SQL Server 2019 CU5](cumulativeupdate5.md#13543133).
 
 ## Improvements and fixes included in this update
 
diff --git a/support/sql/releases/sqlserver-2019/cumulativeupdate9.md b/support/sql/releases/sqlserver-2019/cumulativeupdate9.md
@@ -32,14 +32,16 @@ SELECT UDF1(UDF2());
 …
 ```
 
-A fix will be provided in a future cumulative update. To mitigate this problem, disable Scalar UDF inlining by using either of the following options:
+To mitigate this problem, disable Scalar UDF inlining by using either of the following options:
 
 - Change the definition of UDF2 by adding `WITH INLINE = OFF` to the definition.
 
 - Disable inlining on the database by using `ALTER DATABASE SCOPED CONFIGURATION SET TSQL_SCALAR_UDF_INLINING = OFF`.
 
 For examples of disabling Scalar UDF inlining, see [Disable Scalar UDF Inlining without changing the compatibility level](/sql/relational-databases/user-defined-functions/scalar-udf-inlining#disable-scalar-udf-inlining-without-changing-the-compatibility-level).
 
+This issue is fixed in [SQL Server 2019 CU11](cumulativeupdate11.md#14066089).
+
 ## Improvements and fixes included in this update
 
 A downloadable Excel workbook that contains a summary list of builds, together with their current support lifecycle, is available. The Excel file also contains detailed fix lists for SQL Server 2019 and SQL Server 2017. [Select to download this Excel file now](https://aka.ms/sqlserverbuilds).
diff --git a/support/sql/releases/sqlserver-2022/cumulativeupdate10.md b/support/sql/releases/sqlserver-2022/cumulativeupdate10.md
@@ -27,7 +27,7 @@ This article describes Cumulative Update package 10 (CU10) for Microsoft SQL Ser
 
 SQL Server 2022 CU10 introduced [fix 2714261](#2714261), which causes an issue with `sys.dm_hadr_database_replica_cluster_states` for read-scale availability groups that results in the **Availability Databases** folder in SQL Server Management Studio (SSMS) not showing the databases in the availability group (AG). To mitigate this issue, roll back the patch to CU9.
 
-Microsoft is working on a fix for this issue and it will be available in a future CU.
+This issue is fixed in [SQL Server 2022 CU12](cumulativeupdate12.md#2923126).
 
 ## Improvements and fixes included in this update
 
diff --git a/support/sql/releases/sqlserver-2022/cumulativeupdate11.md b/support/sql/releases/sqlserver-2022/cumulativeupdate11.md
@@ -26,7 +26,7 @@ This article describes Cumulative Update package 11 (CU11) for Microsoft SQL Ser
 
 SQL Server 2022 CU10 introduced [fix 2714261](cumulativeupdate10.md#2714261), which causes an issue with `sys.dm_hadr_database_replica_cluster_states` for read-scale availability groups that results in the **Availability Databases** folder in SQL Server Management Studio (SSMS) not showing the databases in the availability group (AG). To mitigate this issue, roll back the patch to CU9.
 
-Microsoft is working on a fix for this issue and it will be available in a future CU.
+This issue is fixed in [SQL Server 2022 CU12](cumulativeupdate12.md#2923126).
 
 ## Improvements and fixes included in this update
 
diff --git a/support/sql/releases/sqlserver-2022/cumulativeupdate14.md b/support/sql/releases/sqlserver-2022/cumulativeupdate14.md
@@ -50,7 +50,7 @@ App-consistent recovery point generation failed.
 
 The issue arises from a code change in SQL Server 2022 CU14 that checks if a database is online and ready to be frozen. The current solution is to roll back to SQL Server 2022 CU13 and perform the snapshot backup. For more information about how to roll back the package to a previous version, see [Uninstall a Cumulative Update from SQL Server](/sql/sql-server/install/uninstall-a-cumulative-update-from-sql-server).
 
-This issue is fixed in [SQL Server 2022 CU15](../sqlserver-2022/cumulativeupdate15.md#3459086).
+This issue is fixed in [SQL Server 2022 CU15](cumulativeupdate15.md#3459086).
 
 ## Improvements and fixes included in this update
 
diff --git a/support/sql/releases/sqlserver-2022/cumulativeupdate2.md b/support/sql/releases/sqlserver-2022/cumulativeupdate2.md
@@ -35,6 +35,8 @@ If you try to create a new external table, you receive the following error messa
 
 To work around this issue, you can uninstall this cumulative update or add the Driver keyword to the `CONNECTION_OPTIONS` argument. For more information, see [Generic ODBC external data sources may not work after installing Cumulative Update](https://techcommunity.microsoft.com/t5/sql-server-support-blog/generic-odbc-external-data-sources-may-not-work-after-installing/ba-p/3783873).
 
+This issue is fixed in [SQL Server 2022 CU5](cumulativeupdate5.md#2398344).
+
 ## Improvements and fixes included in this update
 
 A downloadable Excel workbook that contains a summary list of builds, together with their current support lifecycle, is available. The Excel file also contains detailed fix lists for SQL Server 2022, SQL Server 2019, and SQL Server 2017. [Select to download this Excel file now](https://aka.ms/sqlserverbuilds).
diff --git a/support/sql/releases/sqlserver-2022/cumulativeupdate3.md b/support/sql/releases/sqlserver-2022/cumulativeupdate3.md
@@ -35,6 +35,8 @@ If you try to create a new external table, you receive the following error messa
 
 To work around this issue, you can uninstall this cumulative update or add the Driver keyword to the `CONNECTION_OPTIONS` argument. For more information, see [Generic ODBC external data sources may not work after installing Cumulative Update](https://techcommunity.microsoft.com/t5/sql-server-support-blog/generic-odbc-external-data-sources-may-not-work-after-installing/ba-p/3783873).
 
+This issue is fixed in [SQL Server 2022 CU5](cumulativeupdate5.md#2398344).
+
 ## Improvements and fixes included in this update
 
 A downloadable Excel workbook that contains a summary list of builds, together with their current support lifecycle, is available. The Excel file also contains detailed fix lists for SQL Server 2022, SQL Server 2019, and SQL Server 2017. [Select to download this Excel file now](https://aka.ms/sqlserverbuilds).
diff --git a/support/sql/releases/sqlserver-2022/cumulativeupdate4.md b/support/sql/releases/sqlserver-2022/cumulativeupdate4.md
@@ -37,6 +37,8 @@ If you try to create a new external table, you receive the following error messa
 
 To work around this issue, you can uninstall this cumulative update or add the Driver keyword to the `CONNECTION_OPTIONS` argument. For more information, see [Generic ODBC external data sources may not work after installing Cumulative Update](https://techcommunity.microsoft.com/t5/sql-server-support-blog/generic-odbc-external-data-sources-may-not-work-after-installing/ba-p/3783873).
 
+This issue is fixed in [SQL Server 2022 CU5](cumulativeupdate5.md#2398344).
+
 ### Issue two
 
 After you install this cumulative update, you may receive incorrect results from queries that meet all of the following conditions:
@@ -61,6 +63,8 @@ After you install this cumulative update, you may receive incorrect results from
 
 To work around this issue, you can either uninstall this cumulative update or enable trace flag (TF) 13166 and then run `DBCC FREEPROCCACHE`.
 
+This issue is fixed in [SQL Server 2022 CU5](cumulativeupdate5.md#2417020).
+
 ## Improvements and fixes included in this update
 
 A downloadable Excel workbook that contains a summary list of builds, together with their current support lifecycle, is available. The Excel file also contains detailed fix lists for SQL Server 2022, SQL Server 2019, and SQL Server 2017. [Select to download this Excel file now](https://aka.ms/sqlserverbuilds).
