| title | description | author | ms.author | ms.reviewer | ms.date | ms.service | ms.subservice | ms.topic | ms.custom | ||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Create a single database | Create a single database in Azure SQL Database using the Azure portal, PowerShell, or the Azure CLI. | WilliamDAssafMSFT | wiassaf | mathoma, randolphwest | 09/17/2024 | azure-sql-database | deployment-configuration | quickstart |
|
In this quickstart, you create a single database in Azure SQL Database using either the Azure portal, a PowerShell script, or an Azure CLI script. You then query the database using Query editor in the Azure portal.
Watch this video in the Azure SQL Database essentials series for an overview of the deployment process:
[!VIDEO https://learn-video.azurefd.net/vod/player?id=0c5d0700-b422-4a46-99bd-84c09ba65804]
- An active Azure subscription. If you don't have one, create a free account.
- Much of this article can be accomplished with the Azure portal alone. Optionally, use the latest version of Azure PowerShell or Azure CLI.
To create databases via Transact-SQL: CREATE DATABASE permissions are necessary. To create a database a login must be either the server admin login (created when the Azure SQL Database logical server was provisioned), the Microsoft Entra admin of the server, a member of the dbmanager database role in master. For more information, see CREATE DATABASE.
To create databases via the Azure portal, PowerShell, Azure CLI, or REST API: Azure RBAC permissions are needed, specifically the Contributor, SQL DB Contributor, or SQL Server Contributor Azure RBAC role. For more information, see Azure RBAC built-in roles.
This quickstart creates a single database in the serverless compute tier.
[!INCLUDE azure-sql-database-free-offer-note]
To create a single database in the Azure portal, this quickstart starts at the Azure SQL page.
Browse to the Select SQL Deployment option page.
Under SQL databases, leave Resource type set to Single database, and select Create.
:::image type="content" source="media/single-database-create-quickstart/select-deployment.png" alt-text="Screenshot of the Select SQL Deployment option page in the Azure portal." lightbox="media/single-database-create-quickstart/select-deployment.png":::
On the Basics tab of the Create SQL Database form, under Project details, select the desired Azure Subscription.
For Resource group, select Create new, enter myResourceGroup, and select OK.
For Database name, enter mySampleDatabase.
For Server, select Create new, and fill out the New server form with the following values:
Server name: Enter mysqlserver, and add some characters for uniqueness. We can't provide an exact server name to use because server names must be globally unique for all servers in Azure, not just unique within a subscription. So enter something like
mysqlserver12345, and the portal lets you know if it's available or not.Location: Select a location from the dropdown list.
Authentication method: Select Use SQL authentication.
Server admin login: Enter azureuser.
Password: Enter a password that meets requirements, and enter it again in the Confirm password field.
Select OK.
Leave Want to use SQL elastic pool set to No.
For Workload environment, specify Development for this exercise.
The Azure portal provides a Workload environment option that helps to preset some configuration settings. These settings can be overridden. This option applies to the Create SQL Database portal page only. Otherwise, the Workload environment option has no impact on licensing or other database configuration settings.
- Choosing the development workload environment sets a few options, including:
- Backup storage redundancy option is locally redundant storage. Locally redundant storage incurs less cost and is appropriate for pre-production environments that do not require the redundance of zone- or geo-replicated storage.
- Compute + storage is General Purpose, Serverless with a single vCore. By default, there is a one-hour auto-pause delay.
- Choosing the Production workload environment sets:
- Backup storage redundancy is geo-redundant storage, the default.
- Compute + storage is General Purpose, Provisioned with 2 vCores and 32 GB of storage. This can be further modified in the next step.
- Choosing the development workload environment sets a few options, including:
Under Compute + storage, select Configure database.
This quickstart uses a serverless database, so leave Service tier set to General Purpose (Most budget-friendly, serverless compute) and set Compute tier to Serverless. Select Apply.
Under Backup storage redundancy, choose a redundancy option for the storage account where your backups will be saved. To learn more, see backup storage redundancy.
Select Next: Networking at the bottom of the page.
:::image type="content" source="media/single-database-create-quickstart/new-sql-database-basics.png" alt-text="Screenshot of the Create SQL Database page, Basic tab from the Azure portal." lightbox="media/single-database-create-quickstart/new-sql-database-basics.png":::
On the Networking tab, for Connectivity method, select Public endpoint.
For Firewall rules, set Add current client IP address to Yes. Leave Allow Azure services and resources to access this server set to No.
:::image type="content" source="media/single-database-create-quickstart/networking.png" alt-text="Screenshot of the Azure portal showing the networking tab for firewall rules." lightbox="media/single-database-create-quickstart/networking.png":::
Under Connection policy, choose the Defaultconnection policy, and leave the Minimum TLS version at the default of TLS 1.2.
Select Next: Security at the bottom of the page.
:::image type="content" source="media/single-database-create-quickstart/networking-connections.png" alt-text="Screenshot that shows the networking tab for policy and encryption." lightbox="media/single-database-create-quickstart/networking-connections.png":::
On the Security page, you can choose to start a free trial of Microsoft Defender for SQL, as well as configure Ledger, Managed identities and Azure SQL transparent data encryption with customer-managed key if you desire. Select Next: Additional settings at the bottom of the page.
On the Additional settings tab, in the Data source section, for Use existing data, select Sample. This creates an
AdventureWorksLTsample database so there's some tables and data to query and experiment with, as opposed to an empty blank database. You can also configure database collation and a maintenance window.Select Review + create at the bottom of the page:
:::image type="content" source="media/single-database-create-quickstart/additional-settings.png" alt-text="Screenshot of the Azure portal showing the Additional settings tab." lightbox="media/single-database-create-quickstart/additional-settings.png":::
On the Review + create page, after reviewing, select Create.
The Azure CLI code blocks in this section create a resource group, server, single database, and server-level IP firewall rule for access to the server. Make sure to record the generated resource group and server names, so you can manage these resources later.
First, install the latest Azure CLI.
[!INCLUDE quickstarts-free-trial-note]
[!INCLUDE azure-cli-prepare-your-environment.md]
[!INCLUDE cli-launch-cloud-shell-sign-in.md]
The following values are used in subsequent commands to create the database and required resources. Server names need to be globally unique across all of Azure so the $RANDOM function is used to create the server name.
Change the location as appropriate for your environment. Replace 0.0.0.0 with the IP address range that matches your specific environment. Use the public IP address of the computer you're using to restrict access to the server to only your IP address.
:::code language="azurecli" source="~/../azure_cli_scripts/sql-database/create-and-configure-database/create-and-configure-database.sh" id="SetParameterValues":::
Create a resource group with the az group create command. An Azure resource group is a logical container into which Azure resources are deployed and managed. The following example creates a resource group named myResourceGroup in the eastus Azure region:
:::code language="azurecli" source="~/../azure_cli_scripts/sql-database/create-and-configure-database/create-and-configure-database.sh" id="CreateResourceGroup":::
Create a server with the az sql server create command.
:::code language="azurecli" source="~/../azure_cli_scripts/sql-database/create-and-configure-database/create-and-configure-database.sh" id="CreateServer":::
Create a firewall rule with the az sql server firewall-rule create command.
:::code language="azurecli" source="~/../azure_cli_scripts/sql-database/create-and-configure-database/create-and-configure-database.sh" id="CreateFirewallRule":::
Create a database with the az sql db create command in the serverless compute tier.
echo "Creating $database in serverless tier" az sql db create \ --resource-group $resourceGroup \ --server $server \ --name $database \ --sample-name AdventureWorksLT \ --edition GeneralPurpose \ --compute-model Serverless \ --family Gen5 \ --capacity 2 You can create a resource group, server, and single database using Azure PowerShell.
First, install the latest Azure PowerShell.
The Azure Cloud Shell is a free interactive shell that you can use to run the steps in this article. It has common Azure tools preinstalled and configured to use with your account.
To open the Cloud Shell, select Try it from the upper right corner of a code block. You can also launch Cloud Shell in a separate browser tab by going to https://shell.azure.com.
When Cloud Shell opens, verify that PowerShell is selected for your environment. Subsequent sessions use Azure CLI in a PowerShell environment. Select Copy to copy the blocks of code, paste it into the Cloud Shell, and press Enter to run it.
The following values are used in subsequent commands to create the database and required resources. Server names need to be globally unique across all of Azure so the Get-Random cmdlet is used to create the server name.
In the following code snippet:
- Replace
0.0.0.0in the ip address range to match your specific environment. - Replace
<strong password here>with a strong password for youradminLogin.
# Set variables for your server and database $resourceGroupName = "myResourceGroup" $location = "eastus" $adminLogin = "azureuser" $password = "<strong password here>" $serverName = "mysqlserver-$(Get-Random)" $databaseName = "mySampleDatabase" # The ip address range that you want to allow to access your server $startIp = "0.0.0.0" $endIp = "0.0.0.0" # Show randomized variables Write-host "Resource group name is" $resourceGroupName Write-host "Server name is" $serverName Create an Azure resource group with New-AzResourceGroup. A resource group is a logical container into which Azure resources are deployed and managed.
Write-host "Creating resource group..." $resourceGroup = New-AzResourceGroup -Name $resourceGroupName -Location $location -Tag @{Owner="SQLDB-Samples"} $resourceGroup Create a server with the New-AzSqlServer cmdlet.
Write-host "Creating primary server..." $server = New-AzSqlServer -ResourceGroupName $resourceGroupName ` -ServerName $serverName ` -Location $location ` -SqlAdministratorCredentials $(New-Object -TypeName System.Management.Automation.PSCredential ` -ArgumentList $adminLogin, $(ConvertTo-SecureString -String $password -AsPlainText -Force)) $server Create a server firewall rule with the New-AzSqlServerFirewallRule cmdlet.
Write-host "Configuring server firewall rule..." $serverFirewallRule = New-AzSqlServerFirewallRule -ResourceGroupName $resourceGroupName ` -ServerName $serverName ` -FirewallRuleName "AllowedIPs" -StartIpAddress $startIp -EndIpAddress $endIp $serverFirewallRule Create a single database with the New-AzSqlDatabase cmdlet.
Write-host "Creating a gen5 2 vCore serverless database..." $database = New-AzSqlDatabase -ResourceGroupName $resourceGroupName ` -ServerName $serverName ` -DatabaseName $databaseName ` -Edition GeneralPurpose ` -ComputeModel Serverless ` -ComputeGeneration Gen5 ` -VCore 2 ` -MinimumCapacity 2 ` -SampleName "AdventureWorksLT" $database Once your database is created, you can use the Query editor (preview) in the Azure portal to connect to the database and query data. For more information, see Azure portal query editor for Azure SQL Database.
In the portal, search for and select SQL databases, and then select your database from the list.
On the page for your database, select Query editor (preview) in the left menu.
Enter your SQL authentication server admin login information or use Microsoft Entra authentication.
[!INCLUDE entra-id]
:::image type="content" source="media/single-database-create-quickstart/query-editor-login.png" alt-text="Screenshot of the Query editor sign-in page in the Azure portal." lightbox="media/single-database-create-quickstart/query-editor-login.png":::
Enter the following query in the Query editor pane.
SELECT TOP 20pc.Nameas CategoryName, p.nameas ProductName FROMSalesLT.ProductCategory pc JOINSalesLT.Product p ONpc.productcategoryid=p.productcategoryid;
Select Run, and then review the query results in the Results pane.
:::image type="content" source="media/single-database-create-quickstart/query-editor-results.png" alt-text="Screenshot of Query editor results." lightbox="media/single-database-create-quickstart/query-editor-results.png":::
Close the Query editor page, and select OK when prompted to discard your unsaved edits.
Keep the resource group, server, and single database to go on to the next steps, and learn how to connect and query your database with different methods.
When you're finished using these resources, you can delete the resource group you created, which will also delete the server and single database within it.
To delete myResourceGroup and all its resources using the Azure portal:
- In the portal, search for and select Resource groups, and then select myResourceGroup from the list.
- On the resource group page, select Delete resource group.
- Under Type the resource group name, enter myResourceGroup, and then select Delete.
Use the following command to remove the resource group and all resources associated with it using the az group delete command - unless you have an ongoing need for these resources. Some of these resources might take a while to create, as well as to delete.
az group delete --name $resourceGroup To delete the resource group and all its resources, run the following PowerShell cmdlet, using the name of your resource group:
Remove-AzResourceGroup -Name $resourceGroupName Want to optimize and save on your cloud spending?
[!div class="nextstepaction"] Start analyzing costs with Cost Management
