Merge pull request #36603 from thesqlsith/2026-02-11-releasenotes-update-derekw

thesqlsith · web-flow · commit b4f5890cd6d5 · 2026-02-12T17:20:32.000-07:00
Release notes update SQL Server 2025
diff --git a/docs/relational-databases/performance/parameter-sensitive-plan-optimization.md b/docs/relational-databases/performance/parameter-sensitive-plan-optimization.md
@@ -4,7 +4,7 @@ description: Learn about Parameter Sensitive Plan Optimization in the Query Stor
 author: MikeRayMSFT
 ms.author: mikeray
 ms.reviewer: derekw, maghan, randolphwest, wiassaf
-ms.date: 10/23/2025
+ms.date: 02/11/2026
 ms.service: sql
 ms.subservice: performance
 ms.topic: concept-article
@@ -332,30 +332,25 @@ PSP optimization provides audit data for the dispatcher plan statement, and any
 
 | Issue | Date discovered | Status | Date resolved |
 | --- | --- | --- | --- |
-| Access Violation exception occurs in Query Store in [!INCLUDE [sssql22-md](../../includes/sssql22-md.md)] under certain conditions. You might encounter Access violation exceptions when PSP optimization Query Store integration is enabled. For more information, see the update in [Parameter Sensitive Plan Optimization, Why?](https://techcommunity.microsoft.com/blog/sqlserver/parameter-sensitive-plan-optimization-why/3836281) | March 2023 | Resolved | August 2023 (CU 7) |
-| Access violation exception can occur on readable secondary replicas under certain conditions in [!INCLUDE [sssql25-md](../../includes/sssql25-md.md)]. You might encounter access violation exceptions when PSP optimization is enabled on a readable secondary database that has been configured to use the [Query Store for readable secondary replicas](query-store-for-secondary-replicas.md) feature. | September 2025 | Has workaround | |
+| Access Violation exception occurs in Query Store in [!INCLUDE [sssql22-md](../../includes/sssql22-md.md)] under certain conditions. You might encounter Access violation exceptions when PSP optimization Query Store integration is enabled. For more information, see the update in [Parameter Sensitive Plan Optimization, Why?](https://techcommunity.microsoft.com/blog/sqlserver/parameter-sensitive-plan-optimization-why/3836281) | March 2023 | Resolved | August 2023 (SQL Server 2022 CU 7) |
+| Access violation exception can occur on readable secondary replicas under certain conditions in [!INCLUDE [sssql25-md](../../includes/sssql25-md.md)]. You might encounter access violation exceptions when PSP optimization is enabled on a readable secondary database that has been configured to use the [Query Store for readable secondary replicas](query-store-for-secondary-replicas.md) feature. | September 2025 | Resolved | January 2026 (SQL Server 2025 CU 1) |
 
-### Has workaround
+### Resolved
 
 #### Access violation exception can occur on readable secondary replicas under certain conditions
 
+(Resolved in January 2026)
+
 Queries that meet the following conditions could experience an access violation when a parameter sensitive plan (PSP) [query variant](#query-variant) can't determine the persisted state of its parent dispatcher statement:
 
 - Executed on a secondary replica
 - Sensitive to parameter sniffing
 - Eligible for parameter sensitive plan (PSP) optimization
 
-**Workaround**: Disable parameter sensitive plan (PSP) optimization on secondary replicas for each database that was onboarded to use the Query Store for readable secondary replicas feature. From within the context of a specific database, issue the following Transact-SQL statement:
-
-```sql
-ALTER DATABASE SCOPED CONFIGURATION FOR SECONDARY
-    SET PARAMETER_SENSITIVE_PLAN_OPTIMIZATION = OFF;
-```
-
-### Resolved
-
 #### Access violation exception occurs in Query Store in SQL Server 2022 under certain conditions
 
+(Resolved in March 2023)
+
 > [!NOTE]  
 > [!INCLUDE [sssql22-md](../../includes/sssql22-md.md)] [Cumulative Update 7](/troubleshoot/sql/releases/sqlserver-2022/cumulativeupdate7) released several fixes for a race condition that can lead to an access violation.
 
diff --git a/docs/sql-server/sql-server-2025-known-issues.md b/docs/sql-server/sql-server-2025-known-issues.md
@@ -4,7 +4,7 @@ description: Known issues, causes, and workarounds for SQL Server 2025 (17.x), c
 author: MikeRayMSFT
 ms.author: mikeray
 ms.reviewer: randolphwest
-ms.date: 12/17/2025
+ms.date: 02/11/2026
 ms.service: sql
 ms.subservice: release-landing
 ms.topic: troubleshooting-known-issue
@@ -31,7 +31,6 @@ The following issues are currently identified:
 - [Issue when setting the backup compression algorithm to ZSTD](#issue-when-setting-the-backup-compression-algorithm-to-zstd)
 - [Local ONNX models not supported on Linux operating systems](#local-onnx-models-not-supported-on-linux-operating-systems)
 - [PBKDF2 hashing algorithm can affect login performance](#pbkdf2-hashing-algorithm-can-affect-login-performance)
-- [Access violation exception can occur on readable secondary replicas under certain conditions](#access-violation-exception-can-occur-on-readable-secondary-replicas-under-certain-conditions)
 - [Vector index](#vector-index)
 - [SQL Server audit events don't write to the Security log](#sql-server-audit-events-dont-write-to-the-security-log)
 - [Upgrade fails if Data Quality Services is installed](#upgrade-fails-if-data-quality-services-is-installed)
@@ -127,32 +126,6 @@ In [!INCLUDE [sssql25-md](../includes/sssql25-md.md)], password-based authentica
 
 For more information, see [CREATE LOGIN](../t-sql/statements/create-login-transact-sql.md) and [Support for Iterated and Salted Hash Password Verifiers in SQL Server 2022 CU12](https://techcommunity.microsoft.com/blog/azuresqlblog/support-for-iterated-and-salted-hash-password-verifiers-in-sql-server-2022-cu12/4087155).
 
-## Access violation exception can occur on readable secondary replicas under certain conditions
-
-Consider a database enabled to use the [Query Store for readable secondaries](../relational-databases/performance/query-store-for-secondary-replicas.md) feature, using the following data definitional language (DDL) command:
-
-```sql
-ALTER DATABASE [Database_Name]
-    FOR SECONDARY
-    SET QUERY_STORE = ON
-    (OPERATION_MODE = READ_WRITE);
-```
-
-Queries that meet the following conditions might experience an access violation when a PSP [query variant](../relational-databases/performance/parameter-sensitive-plan-optimization.md#query-variant) can't determine the persisted state of its parent dispatcher statement:
-
-- Executed on a secondary replica
-- Sensitive to parameter sniffing
-- Eligible for parameter sensitive plan (PSP) optimization
-
-We have identified a fix for a future release of [!INCLUDE [sssql25-md](../includes/sssql25-md.md)].
-
-**Workaround**: Disable PSP on secondaries for each database that was onboarded to use the Query Store for readable secondaries feature. From within the context of a specific database, issue the following Transact-SQL statement:
-
-```sql
-ALTER DATABASE SCOPED CONFIGURATION FOR SECONDARY
-    SET PARAMETER_SENSITIVE_PLAN_OPTIMIZATION = OFF;
-```
-
 ## SQL Server audit events don't write to the Security log
 
 Assume that you configured multiple [!INCLUDE [ssnoversion-md](../includes/ssnoversion-md.md)] audit events to write to the [!INCLUDE [sssql25-md](../includes/sssql25-md.md)] Security log. In this scenario, you notice that all server audits, except the first server audit, don't write. Additionally, when you add the second server audit, you might receive an error that resembles the following message in the [!INCLUDE [ssnoversion-md](../includes/ssnoversion-md.md)] error log:
