Azure SQL Managed Instance Scaling Both Primary & Secondary

ِAhmed Barahim 20 Reputation points
2024-07-11T22:22:43.0366667+00:00

I have two SQL Managed Instances, one is using it as the primary and the other one is for secondary-geo replication .

At the moment both of them have the same specs (Service Tier - Hardware Generation- vCore - Storage), I would like the scale up the hardware Generation from Standard to Premium only for the the primary instance and scale down the vCore for the secondary instance

Is that possible or should both primary & secondary have the same specs?

Azure SQL Database
0 comments No comments
{count} votes

Accepted answer
  1. hossein jalilian 8,080 Reputation points
    2024-07-11T22:56:01.44+00:00

    Thanks for posting your question in the Microsoft Q&A forum.

    You can have different service tiers and hardware generations for your primary and secondary instances. It's also possible to have different vCore counts for your primary and secondary instances.

    While you can have different compute resources, the secondary instance must have at least as much storage as the primary instance. This ensures that the secondary can accommodate all the data from the primary.

    It's generally recommended to scale the secondary instance first before scaling the primary. ensure that the secondary instance has sufficient resources to handle the replication workload from the primary, even if you scale it down


    Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful

    1 person found this answer helpful.
    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. RahulRandive 9,901 Reputation points
    2024-07-12T02:37:40.81+00:00

    Hi @ِAhmed Barahim

    As per the Microsoft document,

    User's image It is recommended that both instances be in the same pricing tier.

    Thank You!

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.