Rediģēt

Kopīgot, izmantojot

Query Store for secondary replicas

  • Raksts

SQL Server 2022 (16.x)

The Query Store for secondary replicas feature enables the same Query Store functionality on secondary replica workloads that is available for primary replicas. When Query Store for secondary replicas is enabled, replicas send the query execution information that would normally be stored in the Query Store back to the primary replica. The primary replica then persists the data to disk within its own Query Store. In essence, there is one Query Store shared between the primary and all secondary replicas. The Query Store exists on the primary replica and stores data for all replicas together. Currently, Query Store for secondary replicas is available with SQL Server 2022 (16.x) instances configured in availability groups.

Important

Query Store for secondary replicas is a preview feature. It is not intended for production deployments. See: SQL Server 2022 (16.0) release notes.

You must enable trace flag 12606 before you can enable Query Store for secondary replicas. To enable the trace flags:

  1. In Windows, launch SQL Server Configuration Manager.
  2. In the list of SQL Server Services, right-click on the SQL Server instance service for your SQL Server 2022 (16.x) instance. Select Properties.
  3. Select the Start Parameters tab. In the Specify a startup parameter: field, add the values: -T12606 and select Add.
  4. The SQL Server instance service must be restarted before the changes will take effect.

Enable Query Store for secondary replicas

Before using Query Store for secondary replicas on a SQL Server instance, you need to have an Always On availability group. Then, enable Query Store for secondary replicas using ALTER DATABASE SET options (Transact-SQL).

If Query Store is not already enabled and in READ_WRITE mode on the primary replica, you must enable it before proceeding. Execute the following for each desired database on the primary replica:

ALTER DATABASE [Database_Name] SET QUERY_STORE = ON;
GO
ALTER DATABASE [Database_Name] SET QUERY_STORE
( OPERATION_MODE = READ_WRITE );

To enable the Query Store on all secondary replicas, connect to the primary replica and execute the following for each desired database. Currently, when the Query Store for secondary replicas is enabled, it is enabled for all secondary replicas.

ALTER DATABASE [Database_Name]
FOR SECONDARY SET QUERY_STORE = ON (OPERATION_MODE = READ_WRITE );
GO

To disable the Query Store on all secondary replicas, connect to the primary replica and execute the following for each desired database:

ALTER DATABASE [Database_Name]
FOR SECONDARY SET QUERY_STORE = OFF;
GO

You can validate that Query Store is enabled on a secondary replica by connecting to the database on the secondary replica and executing the following:

SELECT desired_state, desired_state_desc, actual_state, actual_state_desc, readonly_reason
FROM sys.database_query_store_options;
GO

The following sample results from querying sys.database_query_store_options indicate that the Query Store is in a READ_CAPTURE_SECONDARY state for the secondary. The readonly_reason of 8 indicates that the query was run against a secondary replica. These results indicate that Query Store has been enabled successfully on the secondary replica.

desired_state desired_state_desc actual_state actual_state_desc readonly_reason
4 READ_CAPTURE_SECONDARY 4 READ_CAPTURE_SECONDARY 8

Once enabled, you can use sys.query_store_replicas to verify the health of the Query Store on the secondary replica.

To disable Query Store for secondary replicas, connect to the database on the primary replica and run the following code:

ALTER DATABASE CURRENT
FOR SECONDARY SET QUERY_STORE = OFF;
GO

Replica sets

Currently, when the Query Store for secondary replicas is enabled, it is enabled for all secondary replicas.

A replica set is defined as being all unnamed replicas that share a role (primary, secondary, geo secondary, geo primary), or as being an individual named replica. The data stored about queries can be analyzed as workloads on a replica set basis. Query Store for replicas provides the ability to monitor and adjust the performance of any unique, read-only workloads that might be executing against secondary replicas.

Performance considerations for Query Store for secondary replicas

The channel used by secondary replicas to send query information back to the primary replica is the same channel used to keep secondary replicas up to date. Data is stored in the same tables on the primary replica that Query Store uses for queries executed on the primary replica, which causes the size of Query Store to grow.

Thus, when a system is under significant load, you may notice some slowdown because of the channel being overloaded. Further, the same adhoc query capture issues that exist for Query Store today will continue for workloads run on secondary replicas. Learn more about how to Keep the most relevant data in Query Store.

See also

Next steps