Active Geo Replication ensures business continuity by utilizing readable secondary database replicas. In case of primary database failure, manually failover to secondary database. Secondaries, up to four, can be in same/different regions, used for read-only access.
Click the Azure Resource Graph tab to view the query
//AzureResourceGraphQuery//ProvidesalistofSQLdatabasesthatarenotpartofGeoReplication.resources|wheretype=="microsoft.sql/servers/databases"|summarizesecondaryTypeCount=countif(isnotempty(properties.secondaryType))byname|wheresecondaryTypeCount==0|joinkind=inner(Resources|wheretype=="microsoft.sql/servers/databases")onname|extendparam1="Not part of Geo Replication"|projectrecommendationId="74c2491d-048b-0041-a140-935960220e20",name,id,tags,param1
Auto Failover Groups can encompass one or multiple databases, usually used by the same app.
Failover Groups facilitate disaster recovery by configuring databases on one logical server to replicate to another region's logical server. This streamlines geo-replicated database management, offering a single endpoint for connection routing to replicated databases if the primary server fails.
By default, Azure SQL Database premium tier provisions multiple copies within the same region. For geo redundancy, databases can be set as Zone Redundant, distributing copies across Azure Availability Zones to maintain availability during regional outages.
During transient failures, the application should handle connection retries effectively with Azure SQL Database. No Database layer configuration is needed; instead, the application must be set up for graceful retrying.
Click the Azure Resource Graph tab to view the query
//cannot-be-validated-with-arg
Monitor your Azure SQL Database in Near Real-Time to Detect Reliability Incidents
Impact:HighCategory:Monitoring and AlertingPG Verified:Verified
APRL GUID:7e7daec9-6a81-3546-a4cc-9aef72fec1f7
Description:
Monitoring and alerting are an important part of database operations. When working with Azure SQL Database, make use of Azure Monitor and SQL Insights to ensure that you capture relevant database metrics.
It is highly recommended to use Azure Key Vault (AKV) to store encryption keys related to Always Encrypted configurations, however it is not required. If you are not using AKV, then ensure that your keys are properly backed up and stored in a secure manner.
When using Failover Groups, it is recommended to connect to the Failover Group endpoint instead of individual database endpoints. This allows for automatic redirection to the secondary database in case of a failover, ensuring high availability.