Merge pull request #8636 from MicrosoftDocs/UpdateKnownIssues_PijoCoder040225

Simonx Xu · web-flow · commit e5a8a19e2e0a · 2025-04-03T13:47:36.000+08:00
Update CU articles with fix info for previously known issues
diff --git a/support/sql/releases/includes/av-sesssion-context-2019.md b/support/sql/releases/includes/av-sesssion-context-2019.md
@@ -0,0 +1,12 @@
+---
+ms.author: jopilov
+author: PiJoCoder
+ms.date: 04/02/2025
+ms.custom: sap:SQL resource usage and configuration (CPU, Memory, Storage), evergreen
+---
+
+SQL Server 2019 CU14 introduced a fix [14307204](../sqlserver-2019/cumulativeupdate14.md#14307204) to [address wrong results in parallel plans returned by the built-in SESSION_CONTEXT](https://support.microsoft.com/help/5008114). However, this fix might create access violation dump files when the SESSION is reset for reuse. To mitigate this issue and avoid incorrect results, you can disable the original fix, and also disable the parallelism for the built-in `SESSION_CONTEXT`. To do this, use the following trace flags:
+
+- 11042 - This trace flag disables the parallelism for the built-in `SESSION_CONTEXT`.
+
+- 9432 - This trace flag disables the fix that was introduced in SQL Server 2019 CU14.
diff --git a/support/sql/releases/includes/patching-error-2019.md b/support/sql/releases/includes/patching-error-2019.md
@@ -4,7 +4,7 @@ author: JamesFerebee
 ms.date: 08/20/2024
 ms.custom: sap:Installation, Patching, Upgrade, Uninstall, evergreen
 ---
-SQL Server 2019 CU 27 introduced fix [2994446](../sqlserver-2019/cumulativeupdate27.md#2994446) to make secondary databases in an availability group (AG) startup more reliably. However, this fix causes a problem where AG databases don't start recovery if SQL Server is running in single-user mode. SQL Server Setup runs in single-user mode. As a result of this, if you run Setup and also have SQL replication, change data capture (CDC), or SQL Server Integration Services database (**SSISDB**) enabled on a database in the AG, when the catalog upgrade scripts try to run but can't access the database, setup fails.
+SQL Server 2019 CU27 introduced fix [2994446](../sqlserver-2019/cumulativeupdate27.md#2994446) to make secondary databases in an availability group (AG) startup more reliably. However, this fix causes a problem where AG databases don't start recovery if SQL Server is running in single-user mode. SQL Server Setup runs in single-user mode. As a result of this, if you run Setup and also have SQL replication, change data capture (CDC), or SQL Server Integration Services database (**SSISDB**) enabled on a database in the AG, when the catalog upgrade scripts try to run but can't access the database, setup fails.
 
 After SQL Server Setup initially fails, the SQL Server service then tries to come online again without single-user mode. At that time, the patch upgrade scripts finish successfully and patching is complete. Once startup completes, the issue is resolved and no user action is required.
 
@@ -26,4 +26,4 @@ If you want to prevent the patch from reporting an initial failure, you can perf
 
 - Remove CDC or replication from the database in the AG.
 
-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 CU29](../sqlserver-2019/cumulativeupdate29.md#3418490).
diff --git a/support/sql/releases/includes/patching-error-2022.md b/support/sql/releases/includes/patching-error-2022.md
@@ -4,7 +4,7 @@ author: JamesFerebee
 ms.date: 08/20/2024
 ms.custom: sap:Installation, Patching, Upgrade, Uninstall, evergreen
 ---
-SQL Server 2022 CU 13 introduced fix [2998350](../sqlserver-2022/cumulativeupdate13.md#2998350) to make secondary databases in an availability group (AG) startup more reliably. However, this fix causes a problem where AG databases don't start recovery if SQL Server is running in single-user mode. SQL Server Setup runs in single-user mode. As a result of this, if you run Setup and also have SQL replication, change data capture (CDC), or SQL Server Integration Services database (**SSISDB**) enabled on a database in the AG, when the catalog upgrade scripts try to run but can't access the database, setup fails.
+SQL Server 2022 CU13 introduced fix [2998350](../sqlserver-2022/cumulativeupdate13.md#2998350) to make secondary databases in an availability group (AG) startup more reliably. However, this fix causes a problem where AG databases don't start recovery if SQL Server is running in single-user mode. SQL Server Setup runs in single-user mode. As a result of this, if you run Setup and also have SQL replication, change data capture (CDC), or SQL Server Integration Services database (**SSISDB**) enabled on a database in the AG, when the catalog upgrade scripts try to run but can't access the database, setup fails.
 
 After SQL Server Setup initially fails, the SQL Server service then tries to come online again without single-user mode. At that time, the patch upgrade scripts finish successfully and patching is complete. Once startup completes, the issue is resolved and no user action is required.
 
@@ -26,4 +26,4 @@ If you want to prevent the patch from reporting an initial failure, you can perf
 
 - Remove CDC or replication from the database in the AG.
 
-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 CU16](../sqlserver-2022/cumulativeupdate16.md#3418488).
diff --git a/support/sql/releases/sqlserver-2019/cumulativeupdate14.md b/support/sql/releases/sqlserver-2019/cumulativeupdate14.md
@@ -32,11 +32,7 @@ After you install CU14, a parallel query that runs in batch mode might cause an
 
 ### Issue two
 
-SQL Server 2019 CU14 introduced a [fix to address wrong results in parallel plans returned by the built-in SESSION_CONTEXT](https://support.microsoft.com/help/5008114). However, this fix might create access violation dump files when the `SESSION` is reset for reuse. To mitigate this issue and avoid incorrect results, you can disable the original fix, and also disable the parallelism for the built-in `SESSION_CONTEXT`. To do this, use the following trace flags:
-
-- 11042 - This trace flag disables the parallelism for the built-in `SESSION_CONTEXT`.
-
-- 9432 - This trace flag disables the fix that was introduced in SQL Server 2019 CU14.
+[!INCLUDE [av-sesssion-context-2019](../includes/av-sesssion-context-2019.md)]
 
 ## Improvements and fixes included in this update
 
diff --git a/support/sql/releases/sqlserver-2019/cumulativeupdate15.md b/support/sql/releases/sqlserver-2019/cumulativeupdate15.md
@@ -25,11 +25,7 @@ This article describes Cumulative Update package 15 (CU15) for Microsoft SQL Ser
 
 ### Access violation when session is reset
 
-SQL Server 2019 CU14 introduced a [fix to address wrong results in parallel plans returned by the built-in SESSION_CONTEXT](https://support.microsoft.com/help/5008114). However, this fix might create access violation dump files when the `SESSION` is reset for reuse. To mitigate this issue and avoid incorrect results, you can disable the original fix, and also disable the parallelism for the built-in `SESSION_CONTEXT`. To do this, use the following trace flags:
-
-- 11042 - This trace flag disables the parallelism for the built-in `SESSION_CONTEXT`.
-
-- 9432 - This trace flag disables the fix that was introduced in SQL Server 2019 CU14.
+[!INCLUDE [av-sesssion-context-2019](../includes/av-sesssion-context-2019.md)]
 
 ## Improvements and fixes included in this cumulative update
 
diff --git a/support/sql/releases/sqlserver-2019/cumulativeupdate16.md b/support/sql/releases/sqlserver-2019/cumulativeupdate16.md
@@ -25,11 +25,7 @@ This article describes Cumulative Update package 16 (CU16) for Microsoft SQL Ser
 
 ### Access violation when session is reset
 
-SQL Server 2019 CU14 introduced a [fix to address wrong results in parallel plans returned by the built-in SESSION_CONTEXT](https://support.microsoft.com/help/5008114). However, this fix might create access violation dump files when the `SESSION` is reset for reuse. To mitigate this issue and avoid incorrect results, you can disable the original fix, and also disable the parallelism for the built-in `SESSION_CONTEXT`. To do this, use the following trace flags:
-
-- 11042 - This trace flag disables the parallelism for the built-in `SESSION_CONTEXT`.
-
-- 9432 - This trace flag disables the fix that was introduced in SQL Server 2019 CU14.
+[!INCLUDE [av-sesssion-context-2019](../includes/av-sesssion-context-2019.md)]
 
 ## Improvements and fixes included in this update
 
diff --git a/support/sql/releases/sqlserver-2019/cumulativeupdate17.md b/support/sql/releases/sqlserver-2019/cumulativeupdate17.md
@@ -25,11 +25,7 @@ This article describes Cumulative Update package 17 (CU17) for Microsoft SQL Ser
 
 ### Access violation when session is reset
 
-SQL Server 2019 CU14 introduced a [fix to address wrong results in parallel plans returned by the built-in SESSION_CONTEXT](https://support.microsoft.com/help/5008114). However, this fix might create access violation dump files when the `SESSION` is reset for reuse. To mitigate this issue and avoid incorrect results, you can disable the original fix, and also disable the parallelism for the built-in `SESSION_CONTEXT`. To do this, use the following trace flags:
-
-- 11042 - This trace flag disables the parallelism for the built-in `SESSION_CONTEXT`.
-
-- 9432 - This trace flag disables the fix that was introduced in SQL Server 2019 CU14.
+[!INCLUDE [av-sesssion-context-2019](../includes/av-sesssion-context-2019.md)]
 
 ## Improvements and fixes included in this update
 
diff --git a/support/sql/releases/sqlserver-2019/cumulativeupdate18.md b/support/sql/releases/sqlserver-2019/cumulativeupdate18.md
@@ -25,11 +25,7 @@ This article describes Cumulative Update package 18 (CU18) for Microsoft SQL Ser
 
 ### Access violation when session is reset
 
-SQL Server 2019 CU14 introduced a [fix to address wrong results in parallel plans returned by the built-in SESSION_CONTEXT](https://support.microsoft.com/help/5008114). However, this fix might create access violation dump files when the `SESSION` is reset for reuse. To mitigate this issue and avoid incorrect results, you can disable the original fix, and also disable the parallelism for the built-in `SESSION_CONTEXT`. To do this, use the following trace flags:
-
-- 11042 - This trace flag disables the parallelism for the built-in `SESSION_CONTEXT`.
-
-- 9432 - This trace flag disables the fix that was introduced in SQL Server 2019 CU14.
+[!INCLUDE [av-sesssion-context-2019](../includes/av-sesssion-context-2019.md)]
 
 ## Improvements and fixes included in this update
 
diff --git a/support/sql/releases/sqlserver-2019/cumulativeupdate19.md b/support/sql/releases/sqlserver-2019/cumulativeupdate19.md
@@ -28,11 +28,7 @@ This article describes Cumulative Update package 19 (CU19) for Microsoft SQL Ser
 
 ### Issue one
 
-SQL Server 2019 CU14 introduced a [fix to address wrong results in parallel plans returned by the built-in SESSION_CONTEXT](https://support.microsoft.com/help/5008114). However, this fix might create access violation dump files when the `SESSION` is reset for reuse. To mitigate this issue and avoid incorrect results, you can disable the original fix, and also disable the parallelism for the built-in `SESSION_CONTEXT`. To do this, use the following trace flags:
-
-- 11042 - This trace flag disables the parallelism for the built-in `SESSION_CONTEXT`.
-
-- 9432 - This trace flag disables the fix that was introduced in SQL Server 2019 CU14.
+[!INCLUDE [av-sesssion-context-2019](../includes/av-sesssion-context-2019.md)]
 
 ### Issue two
 
diff --git a/support/sql/releases/sqlserver-2019/cumulativeupdate20.md b/support/sql/releases/sqlserver-2019/cumulativeupdate20.md
@@ -25,11 +25,7 @@ This article describes Cumulative Update package 20 (CU20) for Microsoft SQL Ser
 
 ### Issue one
 
-SQL Server 2019 CU14 introduced a [fix to address wrong results in parallel plans returned by the built-in SESSION_CONTEXT](https://support.microsoft.com/help/5008114). However, this fix might create access violation dump files when the `SESSION` is reset for reuse. To mitigate this issue and avoid incorrect results, you can disable the original fix, and also disable the parallelism for the built-in `SESSION_CONTEXT`. To do this, use the following trace flags:
-
-- 11042 - This trace flag disables the parallelism for the built-in `SESSION_CONTEXT`.
-
-- 9432 - This trace flag disables the fix that was introduced in SQL Server 2019 CU14.
+[!INCLUDE [av-sesssion-context-2019](../includes/av-sesssion-context-2019.md)]
 
 ### Issue two
 
diff --git a/support/sql/releases/sqlserver-2019/cumulativeupdate21.md b/support/sql/releases/sqlserver-2019/cumulativeupdate21.md
@@ -25,11 +25,7 @@ This article describes Cumulative Update package 21 (CU21) for Microsoft SQL Ser
 
 ### Issue one
 
-SQL Server 2019 CU14 introduced a [fix to address wrong results in parallel plans returned by the built-in SESSION_CONTEXT](https://support.microsoft.com/help/5008114). However, this fix might create access violation dump files when the SESSION is reset for reuse. To mitigate this issue and avoid incorrect results, you can disable the original fix, and also disable the parallelism for the built-in `SESSION_CONTEXT`. To do this, use the following trace flags:
-
-- 11042 - This trace flag disables the parallelism for the built-in `SESSION_CONTEXT`.
-
-- 9432 - This trace flag disables the fix that was introduced in SQL Server 2019 CU14.
+[!INCLUDE [av-sesssion-context-2019](../includes/av-sesssion-context-2019.md)]
 
 ### Issue two
 
diff --git a/support/sql/releases/sqlserver-2019/cumulativeupdate22.md b/support/sql/releases/sqlserver-2019/cumulativeupdate22.md
@@ -25,11 +25,7 @@ This article describes Cumulative Update package 22 (CU22) for Microsoft SQL Ser
 
 ### Access violation when session is reset
 
-SQL Server 2019 CU14 introduced a [fix to address wrong results in parallel plans returned by the built-in SESSION_CONTEXT](https://support.microsoft.com/help/5008114). However, this fix might create access violation dump files when the SESSION is reset for reuse. To mitigate this issue and avoid incorrect results, you can disable the original fix, and also disable the parallelism for the built-in `SESSION_CONTEXT`. To do this, use the following trace flags:
-
-- 11042 - This trace flag disables the parallelism for the built-in `SESSION_CONTEXT`.
-
-- 9432 - This trace flag disables the fix that was introduced in SQL Server 2019 CU14.
+[!INCLUDE [av-sesssion-context-2019](../includes/av-sesssion-context-2019.md)]
 
 ## Improvements and fixes included in this update
 
diff --git a/support/sql/releases/sqlserver-2019/cumulativeupdate23.md b/support/sql/releases/sqlserver-2019/cumulativeupdate23.md
@@ -25,11 +25,7 @@ This article describes Cumulative Update package 23 (CU23) for Microsoft SQL Ser
 
 ### Access violation when session is reset
 
-SQL Server 2019 CU14 introduced a [fix to address wrong results in parallel plans returned by the built-in SESSION_CONTEXT](https://support.microsoft.com/help/5008114). However, this fix might create access violation dump files when the SESSION is reset for reuse. To mitigate this issue and avoid incorrect results, you can disable the original fix, and also disable the parallelism for the built-in `SESSION_CONTEXT`. To do this, use the following trace flags:
-
-- 11042 - This trace flag disables the parallelism for the built-in `SESSION_CONTEXT`.
-
-- 9432 - This trace flag disables the fix that was introduced in SQL Server 2019 CU14.
+[!INCLUDE [av-sesssion-context-2019](../includes/av-sesssion-context-2019.md)]
 
 ## Improvements and fixes included in this update
 
diff --git a/support/sql/releases/sqlserver-2019/cumulativeupdate24.md b/support/sql/releases/sqlserver-2019/cumulativeupdate24.md
@@ -25,11 +25,7 @@ This article describes Cumulative Update package 24 (CU24) for Microsoft SQL Ser
 
 ### Issue one: Access violation when session is reset
 
-SQL Server 2019 CU14 introduced a [fix to address wrong results in parallel plans returned by the built-in SESSION_CONTEXT](https://support.microsoft.com/help/5008114). However, this fix might create access violation dump files when the SESSION is reset for reuse. To mitigate this issue and avoid incorrect results, you can disable the original fix, and also disable the parallelism for the built-in `SESSION_CONTEXT`. To do this, use the following trace flags:
-
-- 11042 - This trace flag disables the parallelism for the built-in `SESSION_CONTEXT`.
-
-- 9432 - This trace flag disables the fix that was introduced in SQL Server 2019 CU14.
+[!INCLUDE [av-sesssion-context-2019](../includes/av-sesssion-context-2019.md)]
 
 ### Issue two: Read-scale availability group not displayed in dm_hadr_database_replica_cluster_states
 
diff --git a/support/sql/releases/sqlserver-2019/cumulativeupdate25.md b/support/sql/releases/sqlserver-2019/cumulativeupdate25.md
@@ -25,11 +25,7 @@ This article describes Cumulative Update package 25 (CU25) for Microsoft SQL Ser
 
 ### Access violation when session is reset
 
-SQL Server 2019 CU14 introduced a [fix to address wrong results in parallel plans returned by the built-in SESSION_CONTEXT](https://support.microsoft.com/help/5008114). However, this fix might create access violation dump files when the SESSION is reset for reuse. To mitigate this issue and avoid incorrect results, you can disable the original fix, and also disable the parallelism for the built-in `SESSION_CONTEXT`. To do this, use the following trace flags:
-
-- 11042 - This trace flag disables the parallelism for the built-in `SESSION_CONTEXT`.
-
-- 9432 - This trace flag disables the fix that was introduced in SQL Server 2019 CU14.
+[!INCLUDE [av-sesssion-context-2019](../includes/av-sesssion-context-2019.md)]
 
 ## Improvements and fixes included in this update
 
diff --git a/support/sql/releases/sqlserver-2019/cumulativeupdate26.md b/support/sql/releases/sqlserver-2019/cumulativeupdate26.md
@@ -25,11 +25,7 @@ This article describes Cumulative Update package 26 (CU26) for Microsoft SQL Ser
 
 ### Issue one: Access violation when session is reset
 
-SQL Server 2019 CU14 introduced a [fix to address wrong results in parallel plans returned by the built-in SESSION_CONTEXT](https://support.microsoft.com/help/5008114). However, this fix might create access violation dump files when the SESSION is reset for reuse. To mitigate this issue and avoid incorrect results, you can disable the original fix, and also disable the parallelism for the built-in `SESSION_CONTEXT`. To do this, use the following trace flags:
-
-- 11042 - This trace flag disables the parallelism for the built-in `SESSION_CONTEXT`.
-
-- 9432 - This trace flag disables the fix that was introduced in SQL Server 2019 CU14.
+[!INCLUDE [av-sesssion-context-2019](../includes/av-sesssion-context-2019.md)]
 
 ### Issue two: Possibility of error 1204 due to disabled lock escalation
 
diff --git a/support/sql/releases/sqlserver-2019/cumulativeupdate27.md b/support/sql/releases/sqlserver-2019/cumulativeupdate27.md
@@ -31,11 +31,7 @@ Microsoft is working on a fix for this issue and it will be available in a futur
 
 ### Issue two: Access violation when session is reset
 
-SQL Server 2019 CU14 introduced a [fix to address wrong results in parallel plans returned by the built-in SESSION_CONTEXT](https://support.microsoft.com/help/5008114). However, this fix might create access violation dump files when the SESSION is reset for reuse. To mitigate this issue and avoid incorrect results, you can disable the original fix, and also disable the parallelism for the built-in `SESSION_CONTEXT`. To do this, use the following trace flags:
-
-- 11042 - This trace flag disables the parallelism for the built-in `SESSION_CONTEXT`.
-
-- 9432 - This trace flag disables the fix that was introduced in SQL Server 2019 CU14.
+[!INCLUDE [av-sesssion-context-2019](../includes/av-sesssion-context-2019.md)]
 
 ### Issue three: Patching error for secondary replicas in an availability group with databases enabled replication, CDC, or SSISDB
 
diff --git a/support/sql/releases/sqlserver-2019/cumulativeupdate28.md b/support/sql/releases/sqlserver-2019/cumulativeupdate28.md
@@ -25,11 +25,7 @@ This article describes Cumulative Update package 28 (CU28) for Microsoft SQL Ser
 
 ### Issue one: Access violation when session is reset
 
-SQL Server 2019 CU14 introduced a [fix to address wrong results in parallel plans returned by the built-in SESSION_CONTEXT](https://support.microsoft.com/help/5008114). However, this fix might create access violation dump files when the SESSION is reset for reuse. To mitigate this issue and avoid incorrect results, you can disable the original fix, and also disable the parallelism for the built-in `SESSION_CONTEXT`. To do this, use the following trace flags:
-
-- 11042 - This trace flag disables the parallelism for the built-in `SESSION_CONTEXT`.
-
-- 9432 - This trace flag disables the fix that was introduced in SQL Server 2019 CU14.
+[!INCLUDE [av-sesssion-context-2019](../includes/av-sesssion-context-2019.md)]
 
 ### Issue two: Patching error for secondary replicas in an availability group with databases enabled replication, CDC, or SSISDB
 
@@ -58,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).
 
-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 CU29](../sqlserver-2019/cumulativeupdate29.md#3459328).
 
 ## Improvements and fixes included in this update
 
diff --git a/support/sql/releases/sqlserver-2019/cumulativeupdate29.md b/support/sql/releases/sqlserver-2019/cumulativeupdate29.md
diff --git a/support/sql/releases/sqlserver-2019/cumulativeupdate30.md b/support/sql/releases/sqlserver-2019/cumulativeupdate30.md
diff --git a/support/sql/releases/sqlserver-2019/cumulativeupdate31.md b/support/sql/releases/sqlserver-2019/cumulativeupdate31.md
diff --git a/support/sql/releases/sqlserver-2019/cumulativeupdate32.md b/support/sql/releases/sqlserver-2019/cumulativeupdate32.md
diff --git a/support/sql/releases/sqlserver-2022/cumulativeupdate14.md b/support/sql/releases/sqlserver-2022/cumulativeupdate14.md
