To have the SQL Server Always-On Availability Groups like feature for your Azure SQL Database you can create a Failover Group. It provides the option to have automatic failover for your Azure SQL databases group without the need of changing the application connection string.
The Azure Private Endpoint helps in securing the connections coming to your Azure SQL Database when used we can deny the public network access for the Azure SQL Server and just make it available from a specific VNet using DNS or the Private IP.
SQL Data Sync is a powerful feature, to know about, for providing easy sync between the mix of Azure SQL and On-premise databases.
When using the Azure SQL Database and you have utilization of your database based upon some trends, like users login more during business hours or the database is being used for reporting purposes for the majority of time and only for small duration of a day or week it’s being having hammered down when doing the loads. It’s better to utilize the DbAAS to the best and scale the database up/down to save cost, it can save you big money.
Auditing for Azure SQL Database can be enabled at SQL Server or Database level, using GUI or PowerShell.
An Azure SQL Database can be restored to the same server or to a different server in a different region (Geo-Restore, will cover this in next blog), using Portal or PowerShell for doing this.
To provide business continuity Azure has the option to replicate your database to multiple regions by using Geo-Replication.
When using SQL VM it is important to consider and know what are the best practices for choosing the disk and caching for the SQL Server data, log and tempdb files.
In this blog we’ll see how to restore back an accidentally deleted database.
Taking backup of your Azure SQL database is not possible but there is an alternative to extract data.