Quickstart: Create an Azure SQL Database Managed Instance
This quickstart walks through how to create an Azure SQL Database Managed Instance in the Azure portal.
If you don't have an Azure subscription, create a free account before you begin.
Sign in to the Azure portal
Sign in to the Azure portal.
Create a Managed Instance
The following steps show you how to create a Managed Instance.
- Choose Create a resource in the upper left-hand corner of the Azure portal.
- Locate Managed Instance and then select Azure SQL Managed Instance.
Fill out the Managed Instance form with the requested information, using the information in the following table:
Setting Suggested value Description Subscription Your subscription A subscription in which you have permission to create new resources Managed instance name Any valid name For valid names, see Naming rules and restrictions. Managed instance admin login Any valid user name For valid names, see Naming rules and restrictions. Don't use "serveradmin" as that is a reserved server-level role. Password Any valid password The password must be at least 16 characters long and meet the defined complexity requirements. Collation The collation that you want to use for your Managed Instance If you are migrating databases from SQL Server, check the source collation using
SELECT SERVERPROPERTY(N'Collation')and use that value. For information about collations, see Server-level collations.
Location The location in which you want to create the Managed Instance For information about regions, see Azure Regions. Virtual network Select either Create new virtual network or a valid virtual network and subnet. If a network/subnet is greyed-out it is must be modified to satisfy the network requirements before you select it as a target for the new Managed Instance. For information regarding the requirements for configuring the network environment for a Managed Instance, see Configure a VNet for Azure SQL Database Managed Instance. Resource group A new or existing resource group For valid resource group names, see Naming rules and restrictions.
To use the Managed Instance as an Instance Failover Group secondary, select the checkout and specify the DnsAzurePartner managed instance. This feature is in preview and not shown in the accompanying screenshot.
- Select Pricing tier to size compute and storage resources as well as review the pricing tier options. The General Purpose pricing tier with 32 GB of memory and 16 vCores is the default value.
- Use the sliders or text boxes to specify the amount of storage and the number of virtual cores.
- When complete, choose Apply to save your selection.
- Select Create to deploy the Managed Instance.
Select the Notifications icon to view the status of deployment.
Select Deployment in progress to open the Managed Instance window to further monitor the deployment progress.
For the first instance in a subnet, deployment time is typically much longer than in subsequent instances. Don't cancel the deployment operation because it lasts longer than you expected. Creating the second Managed Instance in the subnet only takes a couple of minutes.
Review resources and retrieve your fully qualified server name
After the deployment completes successfully, review the resources created and retrieve the fully qualified server name for use in later quickstarts.
Open the resource group for your Managed Instance and view its resources that were created for you in the Create a Managed Instance quickstart.
Select your Managed Instance.
On the Overview tab, locate the Host property and copy the fully qualified host address for the Managed Instance.
The name is similar to your_machine_name.a1b2c3d4e5f6.database.windows.net.
- To learn about connecting to a Managed Instance, see:
- For an overview of the connection options for applications, see Connect your applications to Managed Instance.
- For a quickstart showing how to connect to a Managed Instance from an Azure virtual machine, see Configure an Azure virtual machine connection.
- For a quickstart showing how to connect to a Managed Instance from an on-premises client computer using a point-to-site connection, see Configure a point-to-site connection.
- To restore an existing SQL Server database from on-premises to a Managed instance, you can use the Azure Database Migration Service (DMS) for migration to restore from a database backup file or the T-SQL RESTORE command to restore from a database backup file.
- For advanced monitoring of Managed Instance database performance with built-in troubleshooting intelligence, see Monitor Azure SQL Database using Azure SQL Analytics
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.