Question

You manage an Azure SQL Database with a business application deployed across two regions. You have configured an auto-failover group between the primary server (East US) and secondary server (West US). The application's connection string currently points directly to the primary server's fully qualified server name. After a recent regional outage triggered an automatic failover, the application could not reconnect to the database even though the secondary was successfully promoted. What change should you make to ensure the application automatically follows the primary during future failovers?

Accepted Answer

Update the connection string to use the failover group's read-write listener endpoint (<fog-name>.database.windows.net).

Answer

Increase the connection timeout value in the application so it waits longer for the primary server to come back online.

Answer

Update the connection string to point directly to the secondary server's fully qualified name in West US.

Answer

Change the failover policy from Automatic to Manual so the application controls when failover occurs.