What dont I see the "Convert to Standby" on a Geo Replication setup of Azure SQL

Hi Mulla, Tabrez •

Just checking if you got a chance to look at the provided reply.

Please let us know if you are still stuck and have queries.

Thanks

Hi ShaktiSingh,

Thank you for the detailed response. Please find my comments below:

• Only one secondary database replica can be designated for standby.

  We only want a single replica which we will use for DR

• The serverless compute tier isn't supported. Standby replica can't be enabled if the primary or secondary database is in the serverless compute tier.

  We are not using serverless compute

• The DTU purchasing model isn't supported. You can enable a standby replica for databases using the vCore purchasing model only.

  We use vCores Purchasing model

• The Hyperscale service tier isn't supported. Only databases in the General Purpose and Business Critical service tiers can be designated for standby.

• We are using General Purpose service tier

• When using a failover group, standby rights are assigned at the database level, not the failover group level, and must be assigned separately for each database within the failover group.

  Understood and we have 4 databases added to the failover group

• Designating a secondary replica for standby isn't supported when the replica is a secondary replica of a secondary replica (a process known is chaining)

  we are not using any chaining.

And yes, I still do not have a solution to this problem.

Thank you.

Could you please let us know the Compute Tier for your Azure SQL?

GeneralPurpose: Standard-series (Gen5), 2 vCores

Please note below Limitations:

• Only one secondary database replica can be designated for standby.

  We need only one secondary replica which we will use for DR purposes only

• The serverless compute tier isn't supported. Standby replica can't be enabled if the primary or secondary database is in the serverless compute tier.

  We do not use serverless compute

• The DTU purchasing model isn't supported. You can enable a standby replica for databases using the vCore purchasing model only.

  we are using vCore model

• The Hyperscale service tier isn't supported. Only databases in the General Purpose and Business Critical service tiers can be designated for standby.

  GeneralPurpose: Standard-series (Gen5), 2 vCores

• When using a failover group, standby rights are assigned at the database level, not the failover group level, and must be assigned separately for each database within the failover group.

  Understood, we currently have 4 databases in the failover group

• Designating a secondary replica for standby isn't supported when the replica is a secondary replica of a secondary replica (a process known is chaining).

  We are not using chaining

If you want me to check anything else, please do let me know.

Hi Mulla, Tabrez •

Thank you so much for providing the details.

Please let us know the Region also and let me reproduce the same scenario at my end and get back to you.

Thanks in advance for your patience.

Hi Mulla, Tabrez •

Please refer to the scenario reproduced by me for Azure SQL Database in East US2 region:

1). Under Data Mangement section, I went to Replicas and created a replica which shows as below:

Go to the 3 dots shown above in the screenshot on right side and look for option: "Convert to Standby":

Confirm to the prompt as shown above.

Now, the replica will be shown as Standby in the Overview section of the Database.

If you again go the page of Replicas, you will now see an option to "Convert to Geo".

Please share screenshot of the Replica section for you if options appears.

Thanks