Elastic pool Tier of replicated secondary server

Question

Hi Team,

Using active geo replication, I have geo replicated my prod Azure SQL DB to secondary DB. Both DBs are in Elastic pool and in different subscriptions. The tier of elastic pool of secondary server I kept lower as compared to the Primary SQL Server.

After this active geo replication, since my requirement was to make sure after failover, all applications which are connecting to prod db need not change the connection string so in Prod SQL Server, I created a Failover group using same DBs. Now after failover once the secondary db becomes primary one if I face any issues related to low tier of elastic pool can I update the tier of elastic pool of secondary SQL Server (which is primary after failover) to same tier as the primary SQL Server (which is now secondary). Please note I need to make sure there is no impact on primary/secondary DBs/servers.

Please let me know if above is not clear I will explain more.

Thanks,

Salil

Answer 1

Hi @salilsingh-9961

Yes, you can update the tier of the elastic pool on the secondary SQL Server (which becomes the primary after failover) to match the tier of the elastic pool on the primary SQL Server (which becomes the secondary after failover).

However, it's important to note that a Geo-Secondary with a lower compute size is at risk of increased replication and redo lag.

Also, you should take some precautions like you should plan the update carefully to ensure that there is no impact on the primary and secondary databases and servers. You can schedule the update during off-peak hours when there is less load on the servers.

Let us know if you have any questions or need additional information.

Thank you!