Running Microsoft SQL Server on a Linux container in Docker, 15 January 2018 on, Summary Continuing my series of articles about Docker, this one explains how to get up and running with Microsoft SQL Server running in a Linux container (spoiler alert: it's remarkably straightforward). Once we've done that, we'll end up running a simple query against our database from outside our docker container (using each of PowerShell, SQL Server Management Studio (SSMS) and LINQPad). Background Recently I got a new laptop which is not quite as powerful as I would usually buy (my emphasis being more on portability and battery life this time round). For this and various other reasons, I decided that now would be a good opportunity to spend a bit more time looking at Docker and not to install quite as much stuff. As I mentioned in my article, a setup like this could sensibly be used by a software developer who wanted a local SQL Server instance without all the hassle (and probable resource usage, even when not in use) of a full local installation.

1. Microsoft Sql Server Management Studio Tutorial
2. Microsoft Sql Server Management Studio For Mac
3. Microsoft Sql Server On Mac

Since I'm using my laptop PC, I'm using Docker for Windows, but this really is cross-platform so, if you're using a Mac or a Linux machine, you can still follow this guide. That's quite cool. Procedure If you haven't already installed Docker, you need to do that first. I have written for doing so on a Windows machine as there can be a couple of issues under certain circumstances. Once Docker is running, you need to pull the latest MS SQL Server image from Docker Hub. You can see more about this image at, but it's not necessary to visit that link to download the image; you only need to go there if you want more information. Open a PowerShell window ( Win+ X, I - it doesn't need to be in admin mode) and run the following commands: First we're going to pull the image.

It's around 1.35GB when decompressed. Docker pull microsoft/mssql-server-linux:2017-latest Then we can run docker images to confirm that it's there.

NOTE: You don't actually need to pull the image separately before trying to run it. The docker run command will pull the image first if it needs to. We'll demonstrate this in a minute.

Running the container Next you need to run it. To do this you need to accept the license agreement and specify a strong password for the administrator (sa) account. You should also specify the PID if you want something other than the Developer edition (which I don't since that version is now free for dev use). There are lots of other environment variables which you can set and which may be seen at (e.g you can change the internal port not to be 1433 via MSSQLTCPPORT=nnnn).

Docker run -e 'ACCEPTEULA=Y' -e 'SAPASSWORD=Str0ngPassword!' -p 1401:1433 -d -name=tomsslsql microsoft/mssql-server-linux:latest NOTE: When connecting to MS SQL on Linux, you have to connect with a username and password; you can't use Windows Authentication. A note about port mapping Note that the port mapping is specified via -p host port:container port. Thus -p 1401:1433 means that port 1401 on the host (my laptop) is mapped to port 1433 in the container. If you've ever used MS SQL Server before, you probably know that it listens on port 1433 by default.

This means that any connection strings I create from outside the container (i.e. Directvhdl for mac os x. All of them) will need to include port 1401.

Querying through PowerShell Now that our container is running, let's run a simple query to satisfy ourselves that everything is working properly. In your PowerShell window, run the following command which will run the slqcmd tool (from within your image) interactively. Docker exec -it tomsslsql /opt/mssql-tools/bin/sqlcmd -S localhost -U sa After entering the (ahem) Str0ngPassword! We chose earlier you will be greeted with a simple 1 prompt. Run the following two commands: 1 SELECT @@VERSION 2 GO The screenshot shows running the image and then running the query (and its output). Let's leave the image running and try querying it via a couple of other methods. Querying using SQL Server Management Studio 2017 If you haven't got SSMS 2017, you can download it for free from:.

First, you need to connect to your server. Don't forget to specify the port and that this is done by using a comma, e.g. Localhost, 1401. Now let's run our extremely simple query using SSMS: Querying using LINQPad I don't know about you, but I've been a big fan of LINQPad for about eight years now.

First you need to connect to your container in much the same way as for SSMS (don't forget the comma). Then choose Language: SQL and run the query. And that's it. Pretty easy, eh?

An aside about image tagging/versioning On the I noticed that there's a version tagged as latest and another one tagged 2017-latest. It seemed likely that these were one and the same, but I couldn't see anything confirming this, so I decided to find out for myself. Notice that I deliberately chose to run the image tagged latest instead of 2017-latest (which I'd already pulled) and notice that they are actually the same image (they have the same image id and nothing was downloaded). We can think of the image id as being a hash of the image, the point being that each different version of the same image will have a different image id and so, if several differently tagged images have the same image id, then they are, in fact, the same image.

As you can see above, the latest and 2017-latest images have the same image id and therefore mssql-server-linux:latest and mssql-server-linux:2017-latest are the same. Conclusion As you can see, it is trivially easy to get up and running with MS SQL Server on Linux using Docker.

In this article we pulled and ran the latest version of MS SQL Server on Linux and ran a very simple query using PowerShell, SQL Server Management Studio (SSMS) and LINQPad. Don't forget to let me know how you get on in the comments section below and follow me on Twitter for more frequent updates.

By: Last Updated: 2018-03-28 Related Tips: Problem You were writing some T-SQL in your high privilege account and Oh No! Production data was modified. How can you set up your environment to safely write T-SQL and still administer databases?

Solution Microsoft has released a new product that can help in this scenario. We can do the following:. Use SQL Server Operations Studio (SSOS) for developers, by using it with a low privilege account. Use SQL Server Management Server (SSMS) for DBAs, by using it with a high privilege account. By setting up your environment like this you ‘develop’ scripts in your, safe, low privilege account in SSOS and do your DBA work in your high privilege account using SSMS. Review of the main features of SQL Server Operations Studio (SSOS). SSOS is a MSSQL database management tool for Windows, Mac and Linux.

(It does not replace SSMS). You can create server groups for managing connections to systems. It has an integrated terminal, or connection to the host operating system. It has script version control using GIT.

(You need to install that.). It has a configurable widget system built in for making dashboards. It has a KEYBOARD centric focus. With the editor you can “Change all occurrences” of a word in a file. Two ticks ✓ ✓ Very helpful!.

With the editor you can use or create T-SQL code snips. With the editor you can double click an object to ‘peek’ at a definitions of database objects. With the dashboard you can easily search for databases on an instance.

With the dashboard you can easily search for tables and stored procedures in a database. SSOS is based on and like. See this for more details. Heads up on the way it works SSOS has its main menu on the left-hand side. Clicking on the icons takes you the following areas: Server connection management. Task monitoring (Like backups.) Workspaces of files and folders.

The (1) indicates one unsaved file. Search over workspaces files and folders. Version control. The (4) indicates you have 4 scripts to commit to version control.

Here are some connections organized into groups. Just click on that area to see the options. An introductory video Here is the introducing SQL Operations Studio. Details on the download and installation If you would like to install SSOS, go to this site or this site and download the installation file for your system. Tip on installing sqlops on your Mac Note: When installing this product on Windows and Linux I found no issues, but installing it on my Mac meant an Operating system upgrade. It must be =10.12. That meant I had to create space on the Mac by removing unused files.

Then SSOS installed without issue. But then I found MacVIM and MySQL WorkBench did not work so they required a fresh installation. But after all that I could use SSOS on my Mac and connect to a SQL Server Express instance on a Windows laptop. Version Control and Git SSOS is an environment for developers and/or part-time developers and you can use Git for version control. This article is not a Git tutorial, so for those who do not know Git you should check out some tutorials. For those who know Git then you will enjoy using Git in SSOS.

TIP: Create a local repository first. Don’t create a public repository in GitHub unless you are sure you want to do that. Rolling back or ‘pulling’ a previous version of a script can be done once you have a repository. Conclusion SQL Server Operations Studio is a rich and helpful environment for developing code and working with databases.

It ‘fits’ as another tool for the DBA and it is not a replacement for SSMS. Summary of tools The tools we have as DBAs has come a long way since I began in 1984. It is getting a little crowded. Here is a table to help sort it all out. Graphical User Interface Icon Platforms Link Aimed at Summary (from the web site) SQL Server Operations Studio Developers SQL Operations Studio (preview) is a free tool that runs on Windows, macOS, and Linux, for managing SQL Server, Azure SQL Database, and Azure SQL Data Warehouse; wherever they're running. SQL Operations Studio (preview) offers a modern, keyboard-focused T-SQL coding experience that makes your everyday tasks easier with built-in features, such as multiple tab windows, a rich T-SQL editor, IntelliSense, keyword completion, code snippets, code navigation, and source control integration (Git).

Run on-demand T-SQL queries, view and save results as text, JSON, or Excel. Edit data, organize your favorite database connections, and browse database objects in a familiar object browsing experience. SQL Server Management Studio Database Administrators SSMS is an integrated environment for managing any SQL infrastructure, from SQL Server to SQL Database. SSMS provides tools to configure, monitor, and administer instances of SQL. Use SSMS to deploy, monitor, and upgrade the data-tier components used by your applications, as well as build queries and scripts.

Microsoft Sql Server Management Studio Tutorial

Use SQL Server Management Studio (SSMS) to query, design, and manage your databases and data warehouses, wherever they are - on your local computer, or in the cloud. SQL Server Data Tools Developers Data integration SQL Server Data Tools (SSDT) transforms database development by introducing a ubiquitous, declarative model that spans all the phases of database development inside Visual Studio. You can use SSDT Transact-SQL design capabilities to build, debug, maintain, and refactor databases. You can work with a database project, or directly with a connected database instance on or off-premise. Mssql for VS Code Developers An extension for developing Microsoft SQL Server, Azure SQL Database and SQL Data Warehouse everywhere with a rich set of functionalities Command Line Interface Icon Platforms Link Aimed at Summary (from the web site) Sqlcmd Anyone The sqlcmd utility lets you enter Transact-SQL statements, system procedures, and script files at the command prompt, in Query Editor in SQLCMD mode, in a Windows script file or in an operating system (Cmd.exe) job step of a SQL Server Agent job. This utility uses ODBC to execute Transact-SQL batches. Bcp Bulk data loaders The bulk copy program utility (bcp) bulk copies data between an instance of Microsoft SQL Server and a data file in a user-specified format.

Microsoft Sql Server Management Studio For Mac

Mssql-scripter Developers The mssql-scripter tool enables developers, DBAs, and sysadmins to generate CREATE and INSERT T-SQL scripts for database objects in SQL Server, Azure SQL DB, and Azure SQL DW from the command line. Mssql-cli Developers A command-line client for SQL Server with auto-completion and syntax highlighting Sqlpackage Developers SqlPackage.exe is a command line utility that automates database development tasks. Next Steps. See this for more details. Are you into source code? Then check out the source code for.

Microsoft Sql Server On Mac

Start SSMS with your dot one account for high access work and give it a go starting SSOS with your non-dot one account for your ‘developer’ work. Check out more of on MSSQLTips.com. Check out this. Last Updated: 2018-03-28.

Post a comment or let the author know this tip helped. All comments are reviewed, so stay on subject or we may delete your comment. Note: your email address is not published. Required fields are marked with an asterisk (.).Name.Email Email me updates. NOTE. If you want to include code from SQL Server Management Studio (SSMS) in your post, please copy the code from SSMS and paste the code into a text editor like NotePad before copying the code below to remove the SSMS formatting.

Signup for our newsletter I agree by submitting my data to receive communications, account updates and/or special offers about SQL Server from MSSQLTips and/or its Sponsors. I have read the and understand I may unsubscribe at any time.