Azure-pipelines-tasks: Allow Azure SQL Database Deployment task to deploy to an ElasticPool

Created on 20 Dec 2017 · 5Comments · Source: microsoft/azure-pipelines-tasks

Environment

VSTS

Issue Description

I am deploying a database schema using a Dacpac file and an Azure SQL DB deployment task.

The database is created with pricing tier S0.
On the same server there is one Elastic Pool configured, and I'd like the database created by the deployment task to appear within that EP.

Release

Source

marcelloromani

Most helpful comment

Same here, the workarounds don't work for me because the names of the databases are dynamic so I can't create them before hand.

This ticket should be properly solved and shouldn't be closed.

PedroC88 on 14 Oct 2019

👍2

All 5 comments

As a workaround, an empty database with the desired name can be created inside the Elastic Pool via the Azure Portal.
The Azure SQL DB deployment task will then correctly instantiate the schema on that database.

marcelloromani on 22 Dec 2017

👀1

@marcelloromani

Thanks for posting workaround on the thread.

Scenario 1
If you have already existing database in elastic pool, using Azure SQL Dacpac deployment you can directly deploy to database in elastic pool.

Scenario 2
If database doesn't exists in elastic pool, by default it creates db with performance level S0. Using argument _DatabaseServiceObjective_, you can specify performance level like S1, S2 etc but currently creation of db in elastic pool is not supported via SQLPackage.exe

I am following up with SQL team regarding this, till then please follow same workaround as you have suggested.

Workaround
So possible workaround as you suggested is to create empty database in elastic pool via Azure portal and then deploy schema using Azure SQL Dacpac deployment task.