Update known issues

Author: MonicaChenc

support/sql/releases/includes/av-sesssion-context-2019.md

@@ -2,7 +2,7 @@
 ms.author: jopilov
 author: PiJoCoder
 ms.date: 04/02/2025
-ms.custom: sap:SQL resource usage and configuration (CPU, Memory, Storage)
+ms.custom: sap:SQL resource usage and configuration (CPU, Memory, Storage), evergreen
 ---
 
 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:

support/sql/releases/includes/patching-error-2019.md

@@ -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.
 
-A fix for this issue can be found in [SQL Server 2019 CU29](../sqlserver-2019/cumulativeupdate29.md). For more information, see [3418490 in CU29](../sqlserver-2019/cumulativeupdate29.md#3418490).
+This issue is fixed in [SQL Server 2019 CU29](../sqlserver-2019/cumulativeupdate29.md#3418490).

support/sql/releases/includes/patching-error-2022.md

@@ -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.
 
-A fix for this issue can be found in [SQL Server 2022 CU16](../sqlserver-2022/cumulativeupdate16.md). For more information, see [3418488 in CU16](../sqlserver-2022/cumulativeupdate16.md#3418488).
+This issue is fixed in [SQL Server 2022 CU16](../sqlserver-2022/cumulativeupdate16.md#3418488).

support/sql/releases/sqlserver-2019/cumulativeupdate28.md

@@ -54,8 +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).
 
-A fix for this issue can be found in [SQL Server 2019 CU 29](../sqlserver-2019/cumulativeupdate29.md). For more information, see [3459328 in CU29](../sqlserver-2019/cumulativeupdate29.md#3459328)
-
+This issue is fixed in [SQL Server 2019 CU29](../sqlserver-2019/cumulativeupdate29.md#3459328).
 
 ## Improvements and fixes included in this update
 

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).
 
-A fix for this issue can be found in [SQL Server 2022 CU15](../sqlserver-2022/cumulativeupdate15.md). For more information, see [3459086 in CU15](../sqlserver-2022/cumulativeupdate15.md#3459086)
+This issue is fixed in [SQL Server 2022 CU15](../sqlserver-2022/cumulativeupdate15.md#3459086).
 
 ## Improvements and fixes included in this update