Skip to content

Commit 0423181

Browse files
committed
Update cumulativeupdate18.md
1 parent be40be7 commit 0423181

2 files changed

Lines changed: 15 additions & 5 deletions

File tree

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
---
2+
ms.author: jopilov
3+
author: PiJoCoder
4+
ms.date: 05/15/2025
5+
ms.custom: sap:SQL resource usage and configuration (CPU, Memory, Storage), evergreen
6+
---
7+
8+
SQL Server 2022 introduced a fix to address wrong results in parallel plans returned by the built-in `SESSION_CONTEXT`. 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:
9+
10+
- 11042 - This trace flag disables the parallelism for the built-in `SESSION_CONTEXT`.
11+
12+
- 9432 - This trace flag disables the fix that was introduced in SQL Server 2022.
13+
14+
Microsoft is working on a fix for this issue and it will be available in a future CU.

support/sql/releases/sqlserver-2022/cumulativeupdate18.md

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -25,11 +25,7 @@ This article describes Cumulative Update package 18 (CU18) for Microsoft SQL Ser
2525

2626
### Access violation when session is reset
2727

28-
The following issue also applies to SQL Server 2022:
29-
30-
[!INCLUDE [av-sesssion-context-2019](../includes/av-sesssion-context-2019.md)]
31-
32-
Microsoft is working on a fix for this issue and it will be available in a future CU.
28+
[!INCLUDE [av-sesssion-context-2022](../includes/av-sesssion-context-2022.md)]
3329

3430
## Improvements and fixes included in this update
3531

0 commit comments

Comments
 (0)