Exercise - Configure Azure SQL Database - Training

10 minutes

You've now seen the Azure portal, SQL Server Management Studio (SSMS), and SQL notebooks in Azure Data Studio. Other tools are available to you for managing Azure SQL. Two of the most popular are the Azure CLI and Azure PowerShell. They're similar in functionality. This activity focuses on the Azure CLI.

To complete this activity, you can use a PowerShell notebook, which is the same concept as a SQL notebook but the coding language is PowerShell. You can use PowerShell notebooks to take advantage of Azure CLI or Azure PowerShell. This article focuses on Azure CLI commands. For both of these tools, you can also use Azure Cloud Shell, which is an interactive shell environment that you can use through your browser in the Azure portal.

In this exercise, use Cloud Shell. It already includes the Azure CLI and Azure PowerShell modules.

Connecting with Azure Cloud Shell and the Azure CLI

In the example that follows, explore the latency effects of using different connection policies in Azure SQL.

Run all of the commands by Cloud Shell. You can easily copy them and then select Shift+Insert to paste into the terminal.

Note

In PowerShell by using Azure Cloud Shell, you can use the PowerShell Az module or the Azure CLI. In this activity, explore the Azure CLI, but similar commands are available for the PowerShell Az module.

Go to shell.azure.com and sign in to your Azure account, if prompted.
Configure a default resource group and an Azure SQL Database logical server, so you don't have to specify them with every az command. Run the following commands to set some variables. Replace <resource-group> and <your-server> with the values that you used when you created your SQL instance in the previous exercise.
```
resourceGroup="<resource-group>"
logical_server="<your-server>"
databaseName="AdventureWorks"
```
Set the defaults in Cloud Shell to specify your default resource group and Azure SQL Database logical server:
```
az configure --defaults group=$resourceGroup sql-server=$logical_server
```
Run the following command to confirm that the defaults have been set:
```
az configure --list-defaults
```
Run the following command to show all databases in the Azure SQL Database logical server:
```
az sql db list
```
The list of databases is a lot of information. Run the following command if you just want to see specifics for the AdventureWorks database:
```
az sql db show --name $databaseName
```
Run the following command to determine database size and usage:
```
az sql db list-usages --name $databaseName
```

These examples use the az sql db commands. There are also commands related to the Azure SQL Database logical server. They fall under az sql server.

There are similar commands for az sql mi and az sql midb. They're commands for databases within a managed instance, sometimes called managed databases.

For detailed explanations of all the available commands, refer to the Azure CLI documentation.

Manage connection policies with the Azure CLI

One thing for which you might use the Azure CLI or Azure PowerShell commands is updating the connection policy. This update is an example for how you can manage Azure SQL by using a tool like the Azure CLI. In this example, you look at Azure SQL Database and its commands for managing the connection policies. The implementation is similar in Azure SQL Managed Instance.

See what the current policy is by using the Azure CLI.
```
az sql server conn-policy show
```
The results tell you the connection type is Default.

Set the connection policy to Proxy and determine the round-trip time.

# update policy
az sql server conn-policy update --connection-type Proxy
# confirm update
az sql server conn-policy show

To test round-trip time, connect by using SSMS. On your device, open SSMS and connect to your database. Right-click your database and select New Query. Create a new query with the following text, and then select Query > Include Client Statistics. In the results, Wait time on server replies is the best indicator of network latency. You can run this query a few times to get a good average.
```
-- Proxy
SELECT * FROM SalesLT.Product
GO 10
```
After 10 trials, an average wait time on server replies might be something like 46.6000. Depending on your internet connection, your results might vary. Make a note of the time that you observe.
What if you want to make everything Redirect so you can try to achieve reduced latency?

For anything that's outside Azure, you need to allow inbound and outbound communication on ports in the range of 11000 to 11999. Opening these ports is required for the Redirect connection policy.

Note

This is likely already configured on your local device. If you hit errors in the next steps, you might need to enable the ports mentioned earlier. For more information, see Ports beyond 1433 for ADO.NET 4.5.

Update the connection policy and confirm that update with the following two commands.
```
# update policy
az sql server conn-policy update --connection-type Redirect
# confirm update
az sql server conn-policy show
```
To test network latency from the Redirect policy, connect with SSMS on your local device. Create a new query by using the following text, and choose Include Client Statistics for your results. Compare Wait time on server replies with your query for Proxy.
```
-- Redirect
SELECT * FROM SalesLT.Product
GO 10
```
After 10 trials, an average wait time on server replies might be around 25.8000, which is almost half that of the proxy-connection policy. Exact timings vary depending on your connection. The time should be significantly reduced compared to your earlier proxy test.

Set the policy back to default for the next exercise by using the following commands:

# update policy
az sql server conn-policy update --connection-type Default
# confirm update
az sql server conn-policy show

Redirect is faster because after the initial connection you can bypass the gateway and go straight to the database. This bypass means fewer hops, which results in less latency. Less latency helps in preventing bottlenecks, which is especially important for chatty applications. In the performance module, you learn more about how to improve and optimize performance.

Continue

Exercise - Configure Azure SQL Database

Connecting with Azure Cloud Shell and the Azure CLI

Manage connection policies with the Azure CLI

Feedback