Databases are important for most applications, but keeping their schemas consistent across versions and environments can become a sticky date pudding without proper care. Tools like RoundhousE provide streamlined, repeatable, script-based migrations and work like a charm out of the box. If using the very cool and atmospheric Azure SQL Elastic Pools, however, the default behavior lands us adjacent to the pool, not in it. Let’s not be hasty to abandon database host nor migrator; it’s easy to correct this with little configuration.

Not The Desired Databases

RoundhousE is kind to its users and creates databases if they do not exist at the start of a migration. When working with Azure SQL, this creates a single database on the connected database server. That certainly fits as expected behavior, but if you’ve provisioned an elastic pool on your Azure SQL Server, you’ll find it sadly empty after a first-time migration.

Databases can be pushed into the pool (not recommended for physical servers) after the fact from the Azure Portal or CLI, but I’m lazy and would prefer RoundhousE to carry me the whole way through.

Custom Database Create

RoundhousE is as easy to customize as it is to use unconfigured, and provides a flag for overriding the default create database behavior in favor of a custom script (-cds). This script can then leverage the T-SQL instruction for where to create an Azure SQL database: SERVICE_OBJECTIVE. We can adapt RoundhousE’s sample custom create script to set both the service objective and the elastic pool’s name:

USE master
DECLARE @Created bit
SET @Created = 0

IF NOT EXISTS(SELECT * FROM sys.databases WHERE [name] = '')
        Set @Created = 1


SELECT @Created

At runtime, RoundhousE will connect as normal, but will run the above before any migration scripts. The ` {{DatabaseName}} ` token will be filled in automatically, but #REPLACE_ELASTIC_POOL_NAME# will need to be hard-coded, or better yet plugged by some other process.

Using in a CI/CD Pipeline

That works fine for a single elastic pool, but hard-coding names is brittle and may not work across environments. We give the script a little nudge; personally, I use powershell to plug in the elastic pool name from an environment variable, before calling RoundhousE:

$replacedContent = (Get-Content -path $createDbScript -Raw) -replace '#REPLACE_ELASTIC_POOL_NAME#', $env:ElasticPoolName

Set-Content -Path $createDbScript -Value $replacedContent

&$roundhouse_exe_path -c "$env:MyConnectionString" -f "./scripts/" -cds $createDbScript --env $env:Environment --vf MyApp.dll

If you use other kinds of SQL hosts besides elastic pools, you can set a flag to only conditionally use the -cds option, or if you prefer writing SQL, knock yourself out on the create script.

Whether or not you need to get fancy, it’s important to noodle around with our tools in the face of odd behavior, especially if it allows us to use more ideal technologies.