Merge pull request #8296 from MonicaChenc/monicasql2019

Simonx Xu · web-flow · commit 2314760a7860 · 2025-02-25T10:15:12.000+08:00
Update the known issue in SQL Server 2019
diff --git a/support/sql/releases/sqlserver-2019/cumulativeupdate14.md b/support/sql/releases/sqlserver-2019/cumulativeupdate14.md
@@ -38,8 +38,6 @@ SQL Server 2019 CU14 introduced a [fix to address wrong results in parallel plan
 
 - 9432 - This trace flag disables the fix that was introduced in SQL Server 2019 CU14.
 
-Microsoft is working on a fix for this issue and it will be available in a future CU.
-
 ## 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/cumulativeupdate15.md b/support/sql/releases/sqlserver-2019/cumulativeupdate15.md
@@ -31,8 +31,6 @@ SQL Server 2019 CU14 introduced a [fix to address wrong results in parallel plan
 
 - 9432 - This trace flag disables the fix that was introduced in SQL Server 2019 CU14.
 
-Microsoft is working on a fix for this issue and it will be available in a future CU.
-
 ## Improvements and fixes included in this cumulative 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/cumulativeupdate16.md b/support/sql/releases/sqlserver-2019/cumulativeupdate16.md
@@ -31,8 +31,6 @@ SQL Server 2019 CU14 introduced a [fix to address wrong results in parallel plan
 
 - 9432 - This trace flag disables the fix that was introduced in SQL Server 2019 CU14.
 
-Microsoft is working on a fix for this issue and it will be available in a future CU.
-
 ## Improvements and fixes included in this update
 
 > [!IMPORTANT]
diff --git a/support/sql/releases/sqlserver-2019/cumulativeupdate17.md b/support/sql/releases/sqlserver-2019/cumulativeupdate17.md
@@ -31,8 +31,6 @@ SQL Server 2019 CU14 introduced a [fix to address wrong results in parallel plan
 
 - 9432 - This trace flag disables the fix that was introduced in SQL Server 2019 CU14.
 
-Microsoft is working on a fix for this issue and it will be available in a future CU.
-
 ## 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/cumulativeupdate18.md b/support/sql/releases/sqlserver-2019/cumulativeupdate18.md
@@ -31,8 +31,6 @@ SQL Server 2019 CU14 introduced a [fix to address wrong results in parallel plan
 
 - 9432 - This trace flag disables the fix that was introduced in SQL Server 2019 CU14.
 
-Microsoft is working on a fix for this issue and it will be available in a future CU.
-
 ## 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/cumulativeupdate19.md b/support/sql/releases/sqlserver-2019/cumulativeupdate19.md
@@ -34,8 +34,6 @@ SQL Server 2019 CU14 introduced a [fix to address wrong results in parallel plan
 
 - 9432 - This trace flag disables the fix that was introduced in SQL Server 2019 CU14.
 
-Microsoft is working on a fix for this issue and it will be available in a future CU.
-
 ### Issue two
 
 After you install this cumulative update, external data sources using the generic ODBC connector may no longer work. When you try to query external tables that were created before installing this cumulative update, you receive the following error message:
diff --git a/support/sql/releases/sqlserver-2019/cumulativeupdate20.md b/support/sql/releases/sqlserver-2019/cumulativeupdate20.md
@@ -31,8 +31,6 @@ SQL Server 2019 CU14 introduced a [fix to address wrong results in parallel plan
 
 - 9432 - This trace flag disables the fix that was introduced in SQL Server 2019 CU14.
 
-Microsoft is working on a fix for this issue and it will be available in a future CU.
-
 ### Issue two
 
 After you install this cumulative update, external data sources using the generic ODBC connector may no longer work. When you try to query external tables that were created before installing this cumulative update, you receive the following error message:
diff --git a/support/sql/releases/sqlserver-2019/cumulativeupdate21.md b/support/sql/releases/sqlserver-2019/cumulativeupdate21.md
@@ -31,8 +31,6 @@ SQL Server 2019 CU14 introduced a [fix to address wrong results in parallel plan
 
 - 9432 - This trace flag disables the fix that was introduced in SQL Server 2019 CU14.
 
-Microsoft is working on a fix for this issue and it will be available in a future CU.
-
 ### Issue two
 
 This issue is caused by a change introduced in SQL Server 2019 CU20 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:
diff --git a/support/sql/releases/sqlserver-2019/cumulativeupdate22.md b/support/sql/releases/sqlserver-2019/cumulativeupdate22.md
@@ -31,8 +31,6 @@ SQL Server 2019 CU14 introduced a [fix to address wrong results in parallel plan
 
 - 9432 - This trace flag disables the fix that was introduced in SQL Server 2019 CU14.
 
-Microsoft is working on a fix for this issue and it will be available in a future CU.
-
 ## 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/cumulativeupdate23.md b/support/sql/releases/sqlserver-2019/cumulativeupdate23.md
@@ -31,8 +31,6 @@ SQL Server 2019 CU14 introduced a [fix to address wrong results in parallel plan
 
 - 9432 - This trace flag disables the fix that was introduced in SQL Server 2019 CU14.
 
-Microsoft is working on a fix for this issue and it will be available in a future CU.
-
 ## 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
@@ -31,8 +31,6 @@ SQL Server 2019 CU14 introduced a [fix to address wrong results in parallel plan
 
 - 9432 - This trace flag disables the fix that was introduced in SQL Server 2019 CU14.
 
-Microsoft is working on a fix for this issue and it will be available in a future CU.
-
 ### Issue two: Read-scale availability group not displayed in dm_hadr_database_replica_cluster_states
 
 SQL Server 2019 CU24 introduced [fix 2714260](#2714260), 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 CU23.
diff --git a/support/sql/releases/sqlserver-2019/cumulativeupdate25.md b/support/sql/releases/sqlserver-2019/cumulativeupdate25.md
@@ -31,8 +31,6 @@ SQL Server 2019 CU14 introduced a [fix to address wrong results in parallel plan
 
 - 9432 - This trace flag disables the fix that was introduced in SQL Server 2019 CU14.
 
-Microsoft is working on a fix for this issue and it will be available in a future CU.
-
 ## 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,8 +31,6 @@ SQL Server 2019 CU14 introduced a [fix to address wrong results in parallel plan
 
 - 9432 - This trace flag disables the fix that was introduced in SQL Server 2019 CU14.
 
-Microsoft is working on a fix for this issue and it will be available in a future CU.
-
 ### Issue two: Possibility of error 1204 due to disabled lock escalation
 
 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."
diff --git a/support/sql/releases/sqlserver-2019/cumulativeupdate27.md b/support/sql/releases/sqlserver-2019/cumulativeupdate27.md
@@ -37,8 +37,6 @@ SQL Server 2019 CU14 introduced a [fix to address wrong results in parallel plan
 
 - 9432 - This trace flag disables the fix that was introduced in SQL Server 2019 CU14.
 
-Microsoft is working on a fix for this issue and it will be available in a future CU.
-
 ### Issue three: Patching error for secondary replicas in an availability group with databases enabled replication, CDC, or SSISDB
 
 [!INCLUDE [patching-error-2019](../includes/patching-error-2019.md)]
diff --git a/support/sql/releases/sqlserver-2019/cumulativeupdate28.md b/support/sql/releases/sqlserver-2019/cumulativeupdate28.md
@@ -31,8 +31,6 @@ SQL Server 2019 CU14 introduced a [fix to address wrong results in parallel plan
 
 - 9432 - This trace flag disables the fix that was introduced in SQL Server 2019 CU14.
 
-Microsoft is working on a fix for this issue and it will be available in a future CU.
-
 ### Issue two: Patching error for secondary replicas in an availability group with databases enabled replication, CDC, or SSISDB
 
 [!INCLUDE [patching-error-2019](../includes/patching-error-2019.md)]
diff --git a/support/sql/releases/sqlserver-2019/cumulativeupdate29.md b/support/sql/releases/sqlserver-2019/cumulativeupdate29.md
@@ -31,8 +31,6 @@ SQL Server 2019 CU14 introduced a [fix to address wrong results in parallel plan
 
 - 9432 - This trace flag disables the fix that was introduced in SQL Server 2019 CU14.
 
-Microsoft is working on a fix for this issue and it will be available in a future CU.
-
 ## 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/cumulativeupdate30.md b/support/sql/releases/sqlserver-2019/cumulativeupdate30.md
@@ -31,8 +31,6 @@ SQL Server 2019 CU14 introduced a [fix to address wrong results in parallel plan
 
 - 9432 - This trace flag disables the fix that was introduced in SQL Server 2019 CU14.
 
-Microsoft is working on a fix for this issue and it will be available in a future CU.
-
 ## 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).
