Merge pull request #34231 from thesqlsith/patch-4

Update alter-database-scoped-configuration-transact-sql.md

Author: prmerger-automator[bot]

docs/t-sql/statements/alter-database-scoped-configuration-transact-sql.md

@@ -5,7 +5,7 @@ description: Enable several database configuration settings at the individual da
 author: markingmyname
 ms.author: maghan
 ms.reviewer: derekw, jovanpop, wiassaf, mariyaali
-ms.date: 04/17/2025
+ms.date: 05/28/2025
 ms.service: sql
 ms.subservice: t-sql
 ms.topic: reference
@@ -115,6 +115,7 @@ ALTER DATABASE SCOPED CONFIGURATION
     | LEDGER_DIGEST_STORAGE_ENDPOINT = { <endpoint URL string> | OFF }
     | OPTIMIZED_SP_EXECUTESQL = { ON | OFF }
     | OPTIMIZED_HALLOWEEN_PROTECTION = { ON | OFF }
+    | OPTIONAL_PARAMETER_PLAN_OPTIMIZATION = { ON | OFF }
 }
 ```
 
@@ -506,7 +507,7 @@ Causes SQL Server to generate a Showplan XML fragment with the ParameterRuntimeV
 
 #### OPTIMIZED_SP_EXECUTESQL = { ON | OFF }
 
-**Applies to:** [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)]
+**Applies to:** [!INCLUDE [sql-server-2025](../../includes/sssql25-md.md)], [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)] and [!INCLUDE [fabric-sqldb](../../includes/fabric-sqldb.md)]
 
 Enables or disables the compilation serialization behavior of `sp_executesql` when a batch is compiled. The default is `OFF`. Allowing batches which use `sp_executesql` to serialize the compilation process reduces the impact of compilation storms.  A compilation storms refers to a situation where a large number of queries are being compiled simultaneously, leading to performance issues and resource contention.
 
@@ -521,6 +522,21 @@ Enables or disables [optimized Halloween protection](../../relational-databases/
 > [!NOTE]  
 > For database compatibility level 160 or lower, this database scoped configuration has no effect.
 
+#### OPTIONAL_PARAMETER_PLAN_OPTIMIZATION = { ON | OFF }
+
+**Applies to:** [!INCLUDE [sql-server-2025](../../includes/sssql25-md.md)]
+
+Enables or disables the [Optional parameter plan optimization](../../relational-databases/performance/optional-parameter-optimization.md) feature. The default is `ON`.
+
+When enabled, the adaptive plan optimization generates multiple execution plans for queries that include optional parameters. These plans are typically expressed using predicates in the form of:
+
+- `@p IS NULL AND @p1 IS NOT NULL`
+- `@p IS NULL OR @p1 IS NOT NULL`
+
+The feature can choose a more optimal plan at runtime based on whether the parameter is `NULL`, which improves performance for queries that could otherwise default to suboptimal performance for such query patterns.
+
+The default is `ON` starting in database compatibility level 170.
+
 ## Permissions
 
 Requires `ALTER ANY DATABASE SCOPED CONFIGURATION` on the database. This permission can be granted by a user with `CONTROL` permission on a database.