Recently I have been investigating what all the fuss is about Docker and it has been well worth my time as Docker is pretty awesome for automating stuff.
My development environment has typically required installing SQL Server. SQL is a bit of a beast with lots of options and takes time to setup how you want.
However since Microsoft have now created a version of SQL Server that runs on Linux you can run SQL Server in a Linux container with only a few commands.
I am going to assume you already have Docker for windows installed on your development machine. If not head over to Docker and find out how.
The Microsoft guide to setting up SQL Server in a Linux container can be found here.
First you need to download the image. In a powershell window run:
docker pull mcr.microsoft.com/mssql/server:2017-latest
This downloads the latest sql server image.
To run this image run the following:
docker run -e "ACCEPT_EULA=Y" -e "SA_PASSWORD=password"
-p 1433:1433 --name sql
-d mcr.microsoft.com/mssql/server:2017-latest
To run a SQL Server image you are required to accept the terms and conditions and set a default sa password. These are added as environment variables with the -e flag.
You also need to set the ports that your container will run on (1433 is the default SQL port) and give your container a name, in this case “sql”.
If you have already installed SQL Server you will not be able to run the container on the same port as your local install. To solve this you can select a different port.
docker run -e "ACCEPT_EULA=Y" -e "SA_PASSWORD=password"
-p 1434:1433 --name sql
-d mcr.microsoft.com/mssql/server:2017-latest
-p 1434:1433 maps the 1433 port on the container to port 1434 of your local environment.
Once you have run this command you can connect SQL Server Management Studio (SSMS) to (local) or (local),1434 if you are using a different port using the credentials you provided and execute any SQL you like.
If your development environment requires windows authentication this of course is not for you, if it doesn’t you are good to go.
The development environment I have been using has various powershell scripts for setting things up. These assume windows auth. However I have adapted them to take custom credentials.
$credential = Get-Credential $server.ConnectionContext.LoginSecure=$false
$server.ConnectionContext.set_Login($credential.UserName)
$server.ConnectionContext.set_SecurePassword($credential.Password)
The Get-Credential command creates a dialog where you can enter SQL credentials, this is then stored in a variable and used in the rest of the script.
How do I restore a backup file to my container?
Run:
docker exec -it sql mkdir /var/opt/mssql/backup
docker cp database.bak sql:/var/opt/mssql/backup
This creates a backup folder and copies a backup file from your local environment to the container. You can then use management studio to restore the backup file (or you could write a sql script to do it). One thing to note when restoring databases, make sure the files are restored to Linux locations not windows locations.
The only issues I have encountered so far are the lack of support for SSIS packages and no windows auth. There are sql server windows images available which I haven’t tried yet which may work better with some of these options.
Top comments (3)
All very clever but I don't grok why you would want to put your permanent data storage solution in a disposable container.
I probably wouldn't put any production data in a disposable container, but this is a great way to quickly and easily get a development environment up and running with SQL Server, without having to go through the steps of manually installing it.
That said Docker has the concept of volumes which allow you to create and destroy your containers without destroying your data or databases. I have used this (again only in a dev environment) for a while, and I personally like it.
time to learn containers then....
I'll add it to the list