Merge pull request #33799 from AttinderPalSingh/patch-3

prmerger-automator[bot] · web-flow · commit 43b71dc802f0 · 2025-04-21T18:22:09.000Z
Update service-tier-hyperscale-replicas.md
diff --git a/azure-sql/database/service-tier-hyperscale-replicas.md b/azure-sql/database/service-tier-hyperscale-replicas.md
@@ -68,7 +68,6 @@ As a result, named replicas offer several benefits over HA replicas, for what co
 
 - Users connected to a named replica aren't disconnected if the primary replica is scaled up or down.
 - Users connected to the primary replica aren't affected when any named replicas are scaled up or down.
-- Workloads running on any replica - primary or named - are unaffected by long-running queries running on other replicas.
 
 The main goal of named replicas is to enable a broad variety of [read scale-out](read-scale-out.md) scenarios, and to improve Hybrid Transactional and Analytical Processing (HTAP) workloads. Examples of how to create such solutions are available here:
 
