20260204 query store on readable secondaries updates

Author: WilliamDAssafMSFT

azure-sql/database/features-comparison.md

@@ -2,10 +2,10 @@
 title: Compare SQL Database Engine Features
 titleSuffix: Azure SQL Database & Azure SQL Managed Instance
 description: This article compares the database engine features of Azure SQL Database and Azure SQL Managed Instance
-author: danimir
-ms.author: danil
-ms.reviewer: wiassaf, bonova, mathoma, danil, randolphwest
-ms.date: 06/16/2025
+author: WilliamDAssafMSFT
+ms.author: wiassaf
+ms.reviewer: danil, bonova, mathoma, danil, randolphwest
+ms.date: 01/27/2026
 ms.service: azure-sql
 ms.subservice: service-overview
 ms.topic: product-comparison
@@ -97,7 +97,7 @@ The following table lists the major features of SQL Server and provides informat
 | [Operators](/sql/t-sql/language-elements/operators-transact-sql) | Most, see individual operators |Yes, see [T-SQL differences](../managed-instance/transact-sql-tsql-differences-sql-server.md) |
 | [Query Notifications](/sql/relational-databases/native-client/features/working-with-query-notifications) | No | Yes |
 | [Query Store](/sql/relational-databases/performance/monitoring-performance-by-using-the-query-store) | Yes | Yes | 
-| [Query Store for secondary replicas](/sql/relational-databases/performance/query-store-for-secondary-replicas) | No, the Query Store for secondary replicas feature isn't available for Azure SQL Database. Currently, the Query Store on the secondary replica contains information about workloads from the primary replica. | No, the Query Store for secondary replicas feature isn't available for Azure SQL Managed Instance. Currently, the Query Store on the secondary replica contains information about workloads from the primary replica.| 
+| [Query Store for secondary replicas](/sql/relational-databases/performance/query-store-for-secondary-replicas) | [Yes](/sql/relational-databases/performance/query-store-for-secondary-replicas) | [Yes](/sql/relational-databases/performance/query-store-for-secondary-replicas) | 
 | [Machine Learning Services](/sql/advanced-analytics/what-is-sql-server-machine-learning) (_Formerly R Services_)| No | Yes, see [Machine Learning Services in Azure SQL Managed Instance](../managed-instance/machine-learning-services-overview.md) |
 | [Recovery models](/sql/relational-databases/backup-restore/recovery-models-sql-server) | Only Full Recovery that guarantees high availability is supported. Simple and Bulk Logged recovery models aren't available. | Only Full Recovery that guarantees high availability is supported. Simple and Bulk Logged recovery models aren't available. |
 | [Resource governor](/sql/relational-databases/resource-governor/resource-governor) | No | Yes |

azure-sql/database/read-scale-out.md

@@ -2,10 +2,10 @@
 title: Read Queries on Replicas
 titleSuffix: Azure SQL Database & Azure SQL Managed Instance
 description: Azure SQL provides the ability to use the capacity of read-only replicas for read workloads, called Read Scale-Out.
-author: rajeshsetlem
-ms.author: rsetlem
-ms.reviewer: wiassaf, mathoma, randolphwest
-ms.date: 06/13/2025
+author: WilliamDAssafMSFT
+ms.author: wiassaf
+ms.reviewer: rsetlem, mathoma, randolphwest, mikeray
+ms.date: 01/27/2026
 ms.service: azure-sql
 ms.subservice: scale-out
 ms.topic: concept-article
@@ -39,7 +39,7 @@ If your SQL connection string is configured with `ApplicationIntent=ReadOnly`, t
 For Azure SQL Database only, if you wish to ensure that the application connects to the primary replica regardless of the `ApplicationIntent` setting in the SQL connection string, you must explicitly disable read scale-out when creating the database or when altering its configuration. For example, if you upgrade your database from Standard or General Purpose tier to Premium or Business Critical and want to make sure all your connections continue to go to the primary replica, disable read scale-out. For details on how to disable it, see [Enable and disable read scale-out](#enable-and-disable-read-scale-out-for-sql-database).
 
 > [!NOTE]  
-> Query Store and SQL Profiler features are not supported on read-only replicas.
+> SQL Profiler feature is not supported on read-only replicas.
 
 ## Data consistency
 
@@ -229,12 +229,18 @@ In this fashion, creating a geo-replica can provide multiple additional read-onl
 
 ## Feature support on read-only replicas
 
-A list of the behavior of some features on read-only replicas follows:
+Query Store on secondary replicas is supported in Azure SQL Database and Azure SQL Managed Instance. For more information, see [Query Store for readable secondary replicas](/sql/relational-databases/performance/query-store-for-secondary-replicas).
 
 - Auditing on read-only replicas is automatically enabled. For more information about the hierarchy of the storage folders, naming conventions, and log format, see [SQL Database audit log format](audit-log-format.md).
-- [Query Performance Insight for Azure SQL Database](query-performance-insight-use.md) relies on data from the [Query Store](/sql/relational-databases/performance/monitoring-performance-by-using-the-query-store), which currently doesn't track activity on the read-only replica. Query Performance Insight doesn't show queries that execute on the read-only replica.
-- Automatic tuning relies on the Query Store, as detailed in the [Automatic tuning paper](https://www.microsoft.com/research/uploads/prod/2019/02/autoindexing_azuredb.pdf). Automatic tuning only works for workloads running on the primary replica.
-
+- [Query Performance Insight for Azure SQL Database](query-performance-insight-use.md) relies on data from the [Query Store](/sql/relational-databases/performance/monitoring-performance-by-using-the-query-store?view=azuresqldb-current&preserve-view=true). Query Performance Insights `does not` currently support the `replica_group_id` concept which is associated with the [Query Store for readable secondaries](/sql/relational-databases/performance/query-store-for-secondary-replicas?view=azuresqldb-current&preserve-view=true) feature. Data displayed within the Query Performance Insights dashboard will aggregate all runtime and wait statistics data from all replicas.
+- The [Automatic plan correction](/sql/relational-databases/automatic-tuning/automatic-tuning?view=azuresqldb-current&preserve-view=true#automatic-plan-correction) component of the [automatic tuning](/sql/relational-databases/automatic-tuning/automatic-tuning?view=azuresqldb-current&preserve-view=true) feature is supported on read-only replicas. Each database would need to be enabled to support automatic plan correction. See [automatic plan correction for secondary replicas](/sql/relational-databases/performance/query-store-for-secondary-replicas?view=azuresqldb-current&preserve-view=true#enable-automatic-plan-correction-for-secondary-replicas) for more information.
+- [Diagnostic settings in Azure Monitor](/azure/azure-monitor/platform/diagnostic-settings) supports the streaming of Query Store [runtime statistics](metrics-diagnostic-telemetry-logging-streaming-export-configure.md#query-store-runtime-statistics) through Azure diagnostic settings. Two columns are included to help identify the replica source of the telemetry data:
+
+    - `is_primary_b`: A Boolean value indicating whether the data originated from the primary replica (true) or a secondary replica (false)
+    - `replica_group_id`: An integer that corresponds to the replica role
+    
+    These columns are essential for disambiguating metrics and performance data when analyzing workloads across replica sets. When configuring diagnostic settings to stream Query Store runtime statistics to Log Analytics, Event Hubs, or Azure Storage, ensure your queries and dashboards account for these columns to properly segment data by replica role.
+    
 ## Related content
 
 - [Configure a license-free standby replica for Azure SQL Database](standby-replica-how-to-configure.md)

docs/relational-databases/performance/parameter-sensitive-plan-optimization.md

@@ -3,7 +3,7 @@ title: Parameter Sensitive Plan Optimization
 description: Learn about Parameter Sensitive Plan Optimization in the Query Store.
 author: MikeRayMSFT
 ms.author: mikeray
-ms.reviewer: derekw, maghan, randolphwest
+ms.reviewer: derekw, maghan, randolphwest, wiassaf
 ms.date: 10/23/2025
 ms.service: sql
 ms.subservice: performance
@@ -333,19 +333,19 @@ 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 excpetions when PSP optimization is enabled on a readable secondary database that has been configured to use the [Query Store for readable secondaries](query-store-for-secondary-replicas.md) feature. | September 2025 | Has workaround | |
+| 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 | |
 
 ### Has workaround
 
 #### Access violation exception can occur on readable secondary replicas under certain conditions
 
-Queries that meet the following conditions could experience an access violation when a PSP [query variant](#query-variant) can't determine the persisted state of its parent dispatcher statement:
+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 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:
+**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

docs/relational-databases/performance/persisted-stats-secondary-replicas.md

@@ -1,36 +1,36 @@
 ---
 title: Persisted Statistics for Readable Secondary Replicas
-description: Describes functions of auto created statistics on readable secondaries. Introduces in SQL Server 2025.
+description: Describes functions of auto created statistics on readable secondary replicas. Introduces in SQL Server 2025.
 author: MikeRayMSFT
 ms.author: mikeray
-ms.reviewer: randolphwest
-ms.date: 12/08/2025
+ms.reviewer: randolphwest, wiassaf
+ms.date: 01/26/2026
 ms.service: sql
 ms.topic: concept-article
 ms.custom:
   - ignite-2025
-# customer intent: As a data engineer, I want statistics that are created on readable secondaries to be persisted so that my workloads that are running against secondary replicas are optimized.
+# customer intent: As a data engineer, I want statistics that are created on readable secondary replicas to be persisted so that my workloads that are running against secondary replicas are optimized.
 monikerRange: "=azuresqldb-current || >=sql-server-ver17 || >=sql-server-linux-ver17"
 ---
 
-# Persisted statistics for readable secondaries
+# Persisted statistics for readable secondary replicas
 
 [!INCLUDE [sqlserver2025-asdb](../../includes/applies-to-version/sqlserver2025-asdb.md)]
 
-[Query Store for readable secondaries](query-store-for-secondary-replicas.md) is available in [!INCLUDE [sssql25-md](../../includes/sssql25-md.md)] and Azure SQL Database, and the persisted statistics for readable secondaries feature uses the infrastructure that Query Store has in place for readable secondaries.
+With persisted statistics, primary replica retains statistics information as permanent statistics, which can be sent to all secondary replicas. This process occurs automatically without requiring manual intervention. The statistics persistence mechanism uses the Query Store for readable secondary replicas infrastructure.
 
-Query Store for readable secondaries is **on** by default in [!INCLUDE [sssql25-md](../../includes/sssql25-md.md)] and Azure SQL Database.
+[Query Store for readable secondary replicas](query-store-for-secondary-replicas.md) is available in [!INCLUDE [sssql25-md](../../includes/sssql25-md.md)] and Azure SQL Database.
+
+Query Store for readable secondary replicas is **on** by default in [!INCLUDE [sssql25-md](../../includes/sssql25-md.md)] and Azure SQL Database.
 
 ## Background
 
-On readable secondary replicas, statistics can also be automatically created when the [auto create statistics](../../t-sql/statements/alter-database-transact-sql-set-options.md) option is enabled but those statistics are temporary and disappear when an instance is restarted. When statistics on a read-only database or read-only snapshot are missing or stale, the Database Engine creates and maintains temporary statistics in `tempdb`.
+On readable secondary replicas, statistics can also be automatically created when the [auto create statistics](../../t-sql/statements/alter-database-transact-sql-set-options.md) option is enabled, but those statistics are temporary and disappear when an instance is restarted. When statistics on a read-only database or read-only snapshot are missing or stale, the Database Engine creates and maintains temporary statistics in `tempdb`.
 
 When the Database Engine creates temporary statistics, the statistics name is appended with the suffix `_readonly_database_statistic` to differentiate the temporary statistics from the permanent statistics. The suffix `_readonly_database_statistic` is reserved for statistics generated by SQL Server. The reason that this approach was taken was to address workloads that execute against readable secondary replicas that might require distinct statistics that don't exist on the primary replica.
 
 Temporary statistics created on secondary replicas remain visible only to the replica that generated them. The primary replica never directly accesses these temporary statistics objects and is only aware of the permanent statistics object after persistence. When temporary statistics are persisted to the primary replica, they become available to all replicas in the availability group through the synchronization mechanism.
 
-The persistence mechanism uses the Query Store for readable secondaries infrastructure introduced in [!INCLUDE [sssql22-md](../../includes/sssql22-md.md)]. Statistics information is sent to the primary replica where it's persisted as permanent statistics, then synchronized back to all secondary replicas. This process occurs automatically without requiring manual intervention.
-
 ## Support catalog views
 
 To support comparing stats creation or update between secondary and primary, and to assist with understanding where statistics were created, three new columns have been added to the `sys.stats` catalog view:
@@ -98,10 +98,10 @@ ORDER BY sch.[name], obj.[name], s.stats_id;
 
 ## Considerations
 
-The persisted statistics for readable secondaries feature is enabled by default as long as the [auto create statistics](../../t-sql/statements/alter-database-transact-sql-set-options.md) option is enabled and the `READABLE_SECONDARY_TEMPORARY_STATS_AUTO_CREATE` and `READABLE_SECONDARY_TEMPORARY_STATS_AUTO_UPDATE` database scoped configuration options are enabled, which is the default configuration. There's no database-scoped configuration to toggle the feature on and off.
+The persisted statistics for readable secondary replicas feature is enabled by default as long as the [auto create statistics](../../t-sql/statements/alter-database-transact-sql-set-options.md) option is enabled and the `READABLE_SECONDARY_TEMPORARY_STATS_AUTO_CREATE` and `READABLE_SECONDARY_TEMPORARY_STATS_AUTO_UPDATE` database scoped configuration options are enabled, which is the default configuration. There's no database-scoped configuration to toggle the feature on and off.
 
 ## Related content
 
-- [Query Store for readable secondaries](query-store-for-secondary-replicas.md)
+- [Query Store for readable secondary replicas](query-store-for-secondary-replicas.md)
 - [AlwaysOn: Making latest statistics available on Readable Secondary, Read-Only database and Database Snapshot](/archive/blogs/sqlserverstorageengine/alwayson-making-latest-statistics-available-on-readable-secondary-read-only-database-and-database-snapshot)
 - [Statistics for Read-Only Access Databases](../../database-engine/availability-groups/windows/active-secondaries-readable-secondary-replicas-always-on-availability-groups.md#Read-OnlyStats)