Deploy a SQL Server Database to a Microsoft Azure Virtual Machine
Applies To: SQL Server 2016
Use the Deploy a SQL Server Database to a Windows Azure VM wizard to deploy a database from an instance of the Database Engine to SQL Server in a Windows Azure Virtual Machine (VM). The wizard uses a full database backup operation, so it always copies the complete database schema and the data from a SQL Server user database. The wizard also does all of the Azure VM configuration for you, so no pre-configuration of the VM is required.
You cannot use the wizard for differential backups. The wizard will not overwrite an existing database that has the same database name. To replace an existing database on the VM, you must first drop the existing database or change the database name. If there is a naming conflict between the database name for an in-flight deploy operation and an existing database on the VM, the wizard will suggest an appended database name for the in-flight database to enable you to complete the operation.
For a step-by-step walkthrough of this wizard, see Migrating a Database to SQL Server on an Azure VM
To complete this wizard, you must be able to provide the following information and have these configuration settings in place:
The Microsoft account details associated with your Windows Azure subscription.
Your Windows Azure publishing profile.
SQL Server currently supports publishing profile version 2.0. To download the supported version of the publishing profile, see Download Publishing Profile 2.0.
The management certificate uploaded to your Windows Azure subscription. Create the management certificate as follows: makecert -sky exchange -r -n "CN=AzureSGTCert" -pe -a sha1 -len 2048 -ss My "AzureSGTCert.cer" Then, upload it to your Windows Azure subscription. Create and install a management certificate.
The management certificate saved into the personal certificate store on the computer where the wizard is running.
You must have a temporary storage location that is available to the computer where the SQL Server database is hosted. The temporary storage location must also be available to the computer where the wizard is running.
If you are deploying the database to an existing VM, the instance of SQL Server must be configured to listen on a TCP/IP port.
Either a Windows Azure VM or Gallery image you plan to use for creation of the VM must have the SQL Server Cloud Adapter configured and running.
You must configure an open endpoint for your SQL Server Cloud Adapter on the Windows Azure gateway with private port 11435.
In addition, if you plan to deploy your database into an existing Windows Azure VM, you must also be able to provide:
The DNS name of the cloud service that hosts your VM.
Administrator credentials for the VM.
Credentials with Backup operator privileges on the database you plan to deploy, from the source instance of SQL Server.
For more information about running SQL Server in Windows Azure virtual machines, see SQL Server Deployment in Windows Azure Virtual Machines and Getting Ready to Migrate to SQL Server in Windows Azure Virtual Machines.
On computers running Windows Server operating systems, you must use the following configuration settings to run this wizard:
Turn off Enhanced Security Configuration: Use Server Manager > Local Server to set Internet Explorer Enhanced Security Configuration (ESC) to OFF.
The database size limitation for this operation is 1 TB.
This deployment feature is available in SQL Server Management Studio for SQL Server 2014.
This deployment feature is for use only with user databases; deploying system databases is not supported.
The deployment feature does not support hosted services that are associated with an Affinity Group. For example, storage accounts associated with an Affinity Group cannot be selected for use on the Deployment Settings page of this wizard.
SQL Server database versions that can be deployed to a Windows Azure VM using this wizard:
SQL Server 2008
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014
SQL Server database versions running in a Windows Azure VM database can be deployed to:
SQL Server 2012
SQL Server 2014
If there is a naming conflict between the database name for an in-flight deploy operation and an existing database on the VM, the wizard will suggest an appended database name for the in-flight database to enable you to complete the operation.
Note the following guidelines and restrictions when deploying databases that have BLOBS stored in FILESTREAM objects:
The deployment feature cannot deploy a FILESTREAM-enabled database into a new VM. If FILESTREAM is not enabled in the VM before you run the wizard, the database restore operation will fail and the wizard operation will not be able to complete successfully. To successfully deploy a database that uses FILESTREAM, enable FILESTREAM in the instance of SQL Server on the host VM before launching the wizard. For more information, see FILESTREAM (SQL Server).
If your database utilizes In-Memory OLTP, you can deploy the database to an Azure VM without any modifications to the database. For more information, see In-Memory OLTP (In-Memory Optimization).
Note that the following assets must be located in the same geographic region:
Data Disk Storage Service
If the assets listed above are not co-located, the wizard will not be able to complete successfully.
Use the following configuration details to modify settings for a SQL Server database deployment to an Azure VM.
Default path for the configuration file - %LOCALAPPDATA%\SQL Server\Deploy to SQL in WA VM\DeploymentSettings.xml
Configuration file structure
TraceLevel="Debug" <!-- Logging level -->
BackupPath="\\[server name]\[volume]\" <!-- The last used path for backup. Used as default in the wizard. -->
CleanupDisabled = False /> <!-- Wizard will not delete intermediate files and Windows Azure objects (VM, CS, SA). -->
<PublishProfile <!-- The last used publish profile information. -->
Certificate="12A34B567890123ABCD4EF567A8" <!-- The certificate for use in the wizard. -->
Subscription="1a2b34c5-67d8-90ef-ab12-xxxxxxxxxxxxx" <!-- The subscription for use in the wizard. -->
Name="My Subscription" <!-- The name of the subscription. -->
Configuration file values
The database being deployed must be in a normal state, the database must be accessible to the user account running the wizard, and the user account must have permissions to perform a backup operation.
To launch the wizard, use the following steps:
Use SQL Server Management Studio to connect to the instance of SQL Server with the database you want to deploy.
In Object Explorer, expand the instance name, then expand the Databases node.
Right-click the database you want to deploy, select Tasks, and then select Deploy Database to Windows Azure VM…
This page describes the Deploy a SQL Server Database to a Windows Azure VM wizard.
Do not show this page again. - Click this check box to stop the Introduction page from being displayed in the future.
Next - Proceeds to the Source Settings page.
Cancel – Cancels the operation and closes the wizard.
Help – Launches the MSDN Help topic for the wizard.
Use this page to connect to the instance of SQL Server that hosts the database you want to deploy to the Windows Azure VM. You will also specify a temporary location for files to be saved from the local machine before they are transferred to Windows Azure. This can be a shared, network location.
Click Connect… and then specify connection details for the instance of SQL Server that hosts the database to deploy.
Use the Select Database drop-down list to specify the database to deploy.
In the Other Settings field, specify a shared folder that will be accessible to the Windows Azure VM service.
Sign in to Microsoft Azure with your Microsoft account or your organizational account. Your Microsoft or organizational account is in the format of an email address, such as firstname.lastname@example.org. For more information about Azure credentials, see Microsoft Account for Organizations FAQ and Troubleshooting sign-in problems with your organizational account.
Use this page to specify the destination server and to provide details about your new database.
Azure Virtual Machine – Specify details for the VM that will host the SQL Server database:
Cloud Service name – Specify the name of the service that hosts the VM. To create a new Cloud Service, specify a name for the new Cloud Service.
Virtual Machine name – Specify the name of the VM that will host the SQL Server database. To create a new Windows Azure VM, specify a name for the new VM.
Settings – Use the Settings button to create a new VM to host the SQL Server database. If you are using an existing VM, the information you provide will be used to authenticate your credentials.
Storage account – Select the storage account from the drop-down list. To create a new storage account, specify a name for the new account. Note that storage accounts associated with an Affinity Group will not be available in the drop-down list.
Target Database – Specify details for the target database.
Server Connection – Connection details for the server.
Database – Specify or confirm the name of a new database. If the database name already exists on the destination SQL Server instance, we suggest that you specify a modified database name.
Use this page to review the specified settings for the operation. To complete the deploy operation using the specified settings, click Finish. To cancel the deploy operation and exit the wizard, click Cancel.
There may be manual steps required to deploy database details to the SQL Server database on the Windows Azure VM. These steps will be outlined in detail for you.
This page reports the success or failure of the deploy operation, showing the results of each action. Any action that encountered an error will have an indication in the Result column. Click the link to view a report of the error for that action.
Click Finish to close the wizard.
Cloud Adapter for SQL Server
Database Lifecycle Management
Export a Data-tier Application
Import a BACPAC File to Create a New User Database
Azure SQL Database Backup and Restore
SQL Server Deployment in Windows Azure Virtual Machines
Getting Ready to Migrate to SQL Server in Windows Azure Virtual Machines