Azure SQL Database Read-Scale Out: Offloading Read-Only Workloads
Learn how to use the ApplicationIntent=ReadOnly property in Azure SQL Database to offload reporting workloads from the primary node to a read-only replica.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how to use the ApplicationIntent=ReadOnly property in Azure SQL Database to offload reporting workloads from the primary node to a read-only replica.
Use readable secondary replicas in Azure SQL Hyperscale to run reporting queries without competing with OLTP writes on the primary.
Learn how to route read-only workloads to a secondary replica in Premium and Business Critical tiers using ApplicationIntent=ReadOnly, and how to verify the routing while accounting for replication lag.
Learn how to offload read traffic in Azure SQL Database Premium and Business Critical tiers with Read‑Scale‑Out, verify routing, monitor replication lag, and understand the key trade‑offs.
Route read-only workloads to a secondary replica in Azure SQL Database using ApplicationIntent=ReadOnly, with notes on consistency, tier coverage and verification caveats.
Learn how Azure SQL Hyperscale read scale‑out lets you add up to 30 read‑only replicas without extra storage cost, how to route traffic with ApplicationIntent=ReadOnly, and the key trade‑offs—replication lag, replica limits, and compute‑only pricing.