Use SQL databases on Azure Stack


This topic applies only to Azure Stack Technical Preview 2.

Use the SQL Server resource provider adapter to expose SQL databases as a service of Azure Stack. After you install the resource provider and connect it to a SQL Server instance, you and your users can create databases for cloud-native apps, websites that are based on SQL, and workloads that are based on SQL without having to provision a virtual machine (VM) that hosts SQL Server each time.

SQL Server resource provider adapter architecture

The resource provider does not offer all the database management capabilities of Azure SQL Database. For example, elastic database pools and the ability to dial database performance up and down automatically aren't available. However, the resource provider does support the same create, read, update, and delete (CRUD) operations that available in Azure SQL Database.

The resource provider is made up of three components:

  • The SQL resource provider adapter VM, which encompasses the resource provider process and the servers that host SQL Server.
  • The resource provider itself, which processes provisioning requests and exposes database resources.
  • Servers that host SQL Server, which provide capacity for databases.

The following conceptual diagram shows these components and the steps that you go through when you deploy the resource provider, set up a server that hosts SQL Server, and then create a database.

Azure Stack SQL resource provider adapter simple architecture

To deploy the SQL provider on a system that does not have internet access, you can copy the file SQL 2014 SP1 Enterprise Evaluation ISO to a local file share and provide that share name when prompted (see below).


The deployment script will perform retries, if necessary, to accommodate less reliable network connections or if an operation exceeds a timeout.

Steps to deploy the resource provider

  1. Download the SQL Server RP installer executable file to the Console VM and extract the files. You can optionally download to another machine and copy the file to the Azure Stack console VM.

  2. Open an elevated PowerShell console and change to the directory where you extracted the files.

  3. Run the DeploySqlProvider.ps1 script.

The script does all of the following:

  • If necessary, download a compatible version of Azure PowerShell.
  • Create a wildcard certificate to secure communication between the resource provider and Azure Resource Manager.
  • Download an evaluation build of SQL Server SP1 from the internet or from a local file share.
  • Upload the certificate and all other artifacts to a storage account on your Azure Stack.
  • Publish gallery package so that you can deploy SQL database through the gallery.
  • Deploy a VM using the default Windows Server 2012 R2 image that comes with Azure Stack.
  • Register a local DNS record that maps to your resource provider VM.
  • Register your resource provider with the local Azure Resource Manager.
  • Connect the resource provider to the SQL server instance on the RP VM

Use “sa” for username and the password that you used when you deployed the resource provider VM.

Either specify at least the required parameters on the command line, or, if you run without any parameters, you will be prompted to enter them.

Here's an example you can run from the PowerShell prompt:

$vmLocalAdminPass = ConvertTo-SecureString "P@ssw0rd1" -AsPlainText -Force
$vmLocalAdminCreds = New-Object System.Management.Automation.PSCredential ("sqlrpadmin", $vmLocalAdminPass)

$AADAdminPass = ConvertTo-SecureString "P@ssw0rd1" -AsPlainText -Force
$AADAdminCreds = New-Object System.Management.Automation.PSCredential ("", $AADAdminPass)

.\DeploySQLProvider.ps1 -AadTenantDirectoryName "" -AzCredential $AADAdminCreds -VMLocalCredential $vmLocalAdminCreds -ResourceGroupName "System.Sql" -VmName "SystemSqlRP"


Parameter Name Description Comment or Default Value
AadTenantDirectoryName The Azure Active Directory Name required
AzCredential Azure Stack Service Admin account credential (use the same account as you used for deploying Azure Stack) required
VMLocalCredential This is used for the local administrator account of the SQL resource provider VM; this password will also be used for the SQL sa account required
ResourceGroupName Resource Group for the items created by this script Microsoft-SQL-RP1
VmName Name of the VM holding the resource provider sqlrp
DependencyFilesLocalPath Path to a local share containing the SQL ISO if you did an offline deployment. You can download SQL 2014 SP1 Enterprise Evaluation ISO from the Microsoft Download Center. leave blank to download from the internet
MaxRetryCount Each operation will be retried if there is a failure 2
RetryDuration Timeout between retries, in seconds 120
CleanupMode Cleanup the resource provider No
DebugMode Prevents automatic cleanup on failure No

This should get your SQL Server resource provider up and running in about 45 minutes (depending on your hardware and download speed). Make sure you reopen your browser before proceeding with the following steps.


If the installation takes more than 90 minutes, it may fail and you will see a failure message on the screen and in the log file, but the deployment will be retried from the failing step. Systems that do not meet the minimum required memory and core specifications may not be able to deploy the SQL RP.

Verify the deployment using the Azure Stack Portal

  1. On the Console VM desktop, click Microsoft Azure Stack Portal and sign in to the portal as the service admin.

  2. Verify that the deployment succeeded. Click Resource Groups > click the resource group you used (default is Microsoft-SQL-RP1), and then make sure that the essentials part of the blade (upper half) reads date (Succeeded).

    Verify Deployment of the SQL RP

  3. Verify that the registration succeeded. Click Resource providers, and then look for SQL Resource Provider:

    Verify the SQL RP was registered

Provide capacity by connecting it to a hosting SQL server

  1. Sign in to the Azure Stack POC portal as a service admin

  2. Click Resource Providers > SQL Resource Provider > SQL Hosting Servers > +Add.

    The SQL Hosting Servers blade is where you can connect the SQL Server Resource Provider to actual instances of SQL Server that serve as the resource provider’s backend.

    Hosting Servers

  3. Fill the form with the connection details of your SQL Server instance. By default, a preconfigured SQL Server called “SQLRP” with the administrator username “sa” and the password you called out in the "LocalCredential" parameter is running on the VM.

Create your first SQL Database to test your deployment

  1. Sign in to the Azure Stack POC portal as service admin.

  2. Click + New >Data + Storage" > SQL Server Database (preview) > Add Add a database

  3. Fill in the form with database details, including a Server Name, Server Admin Login, and Password for a new virtual server in the New Server blade.

    Virtual database server

    The virtual server is an artificial construct. It doesn’t map to the SQL Server itself but instead manifests through the username inside the connection string, which the resource provider generates at the end of this process. Note the password you input separately for the virtual server. The portal will never show the password.

  4. You're asked to pick a pricing tier for your database.

    Pick a pricing tier

    Tiers are not implemented in this version, but their consumption is tracked by the Azure Resource Manager as a way to showcase the differentiation you can create in quota enforcement etc.

  5. Submit the form and wait for the deployment to complete.

  6. In the resulting blade, notice the “Connection string” field. You can use that string in any application that requires SQL Server access (for example, a web app) in your Azure Stack.

    Retrieve the connection string

Add Capacity

Add Capacity by adding additional SQL hosts in the Azure Stack portal. If you wish to use another instance of SQL instead of the one installed on the provider VM, click Resource Providers > SQL Resource Provider > SQL Hosting Servers > +Add.

Next steps

Create plans and offers to make SQL databases available for tenants. You will need to create a plan, add the Microsoft.Sql service to the plan, add an existing Tier Quota, or create a new one. If you create a quota, you can specify the capacity to allow the tenant. Create plans and offers to include databases

Try other PaaS services like the MySQL Server resource provider and the App Services resource provider.