Blog Post

Azure Database Support Blog
3 MIN READ

Read-only queries are now captured in the Primary Query Store.

Anuradha_A's avatar
Anuradha_A
Icon for Microsoft rankMicrosoft
Jan 14, 2026

Recent backend improvements now consolidate telemetry from read-only replicas into the primary database’s Query Store. As a result, read-only workload executed on secondary replicas may appear under the primary’s Query Store and Query Performance Insight on Azure Portal, even though execution still occurs on the replica. This behavior is by design and enabled to provide better end-to-end performance visibility. The document also outlines quick methods via T‑SQL and SSMS Query Store reports to verify whether a query actually ran on the primary or secondary replica.

1) Scope & Symptoms Observed symptom: Queries for the read‑only replica are now visible in the primary database’s Query Store. Please verify the application’s connection string and check whether ...
Updated Feb 03, 2026
Version 3.0
Anuradha_A's avatar
Anuradha_A
Icon for Microsoft rankMicrosoft
Jan 22, 2026

m60freeman​ Query that are being executed on either on Primary or secondary now it will be visible in the Primary Query Store and you can run the DMVs to query explicitly either Primary or Secondary to get the details.

Regarding the CASE statement, you can use this in the query to get the Named Replica:
CASE qrs.replica_group_id WHEN 1 THEN 'PRIMARY' WHEN 2 THEN 'SECONDARY' WHEN 3 THEN 'GEO SECONDARY' WHEN 4 THEN 'GEO HA SECONDARY' ELSE CONCAT('NAMED REPLICA_', qrs.replica_group_id)