See the explanation part for the complete Solution.
Explanation:
To configure high availability for dbl, you can use the failover groups feature of Azure SQL Database. Failover groups allow you to manage the replication and failover of a group of databases across different regions with the same connection strings1. You can choose all, or a subset of, user databases in a logical server to be replicated to another logical server in a different region. You can also specify the failover policy, such as manual or automatic, and the grace period for data loss.
Here are the steps to create a failover group for dbl:
* Using the Azure portal:
* Go to the Azure portal and select your Azure SQL Database server that hosts dbl.
* Select Failover groups in the left menu and click on Add group.
* Enter a name for the failover group and select a secondary region that is different from the primary region.
* Click on Create a new server and enter the details for the secondary server, such as server name, admin login, password, and subscription.
* Click on Select existing database(s) and choose dbl from the list of databases on the primary server.
* Click on Configure failover policy and select the failover mode, grace period, and read-write failover endpoint mode according to your preferences.
* Click on Create to create the failover group and start the replication of dbl to the secondary server.
* Using PowerShell commands:
* Install the Azure PowerShell module and log in with your Azure account.
* Run the following command to create a new server in the secondary region: New-AzSqlServer - ResourceGroupName <your-resource-group-name> -ServerName <your-secondary-server-name>
-Location "<secondary-region-name>" -SqlAdministratorCredentials $(New-Object -TypeName System.Management.Automation.PSCredential -ArgumentList "<your-admin-login>",
$(ConvertTo-SecureString -String "<your-password>" -AsPlainText -Force))
* Run the following command to create a new failover group with dbl: New- AzSqlDatabaseFailoverGroup -ResourceGroupName <your-resource-group-name> -ServerName
<your-primary-server-name> -PartnerResourceGroupName <your-resource-group-name> - PartnerServerName <your-secondary-server-name> -FailoverGroupName <your-failover-group- name> -Database dbl -FailoverPolicy <manual-or-automatic> -GracePeriodWithDataLossHours
<grace-period-in-hours> -ReadWriteFailoverEndpoint "<enabled-or-disabled>"
* You can modify the parameters of the command according to your preferences, such as the failover policy, grace period, and read-write failover endpoint mode.
These are the steps to create a failover group for dbl

Reference:
https://docs.microsoft.com/en-us/azure/azure-sql/database/metrics-diagnostic-telemetry-logging-streaming- export-configure?tabs=azure-portal#configure-the-streaming-export-of-diagnostic-telemetry

Explanation:

Reference:
https://docs.microsoft.com/en-us/azure/azure-sql/database/purchasing-models
https://docs.microsoft.com/en-us/azure/azure-sql/database/single-database-create-arm-template-quickstart

Explanation:

For rowstore tables and indexes, use the data compression feature to help reduce the size of the database. In addition to saving space, data compression can help improve performance of I/O intensive workloads because the data is stored in fewer pages and queries need to read fewer pages from disk.
Use columnstore archival compression to further reduce the data size for situations when you can afford extra time and CPU resources to store and retrieve the data.