question

VijayKumar768 avatar image
2 Votes"
VijayKumar768 asked AlbertoMorillo edited

Hyperscale Replicas in Azure SQL DB

Hi Team,

We are planning to upgrade one of our Azure DB.

Currently, the Azure DB (Single DB) contains 1Primary(West US)+1 Secondary Replica (East US).

My doubt is, while i try to upgrade to Hyperscale i found that below feature:
198966-image.png



My confusion is what is the difference High-Availability Secondary Replicas from the already existing Secondary Replicat(East US)?

azure-sql-database
image.png (16.9 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

AlbertoMorillo avatar image
1 Vote"
AlbertoMorillo answered AlbertoMorillo edited

You can have primary and secondary replica in Hyperscale service tier.

  1. Primary replica serves read and write operations

  2. Secondary replica provides read scale-out, high availability, and geo-replication

Secondary replicas are always read-only, and can be of three different types:

  • High Availability replica (recommended). This one can help you get a higher SLA.

  • Named replica (in Preview, no guaranteed SLA)

  • Geo-replica (in Preview, no guaranteed SLA)

Replicas are optional and not required on Hyperscale. What will happen is that if the primary replicas for any reason is not available, Micosoft Azure will need to spin up a new (compute) replica from scratch (as there are no HA replica available) so that can take some time (minutes, usually) which means that your service will not be available that amount time. Having an HA replica, drastically diminish the time in which the database is not available.

That is how Hyperscale replicas differ from geo-replication replicas on other Azure SQL offerings (flavors).

-




5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.