For the first time, SQL Server 2017 allows users to install the product on Linux. This opens the doors for working with fully-featured SQL Server database engines on MacOS through freely distributable Docker containers. With the addition of a new graphical user interface that's in public preview, Mac users can now leverage the same industry-leading database platform that has previously only been available to Windows users, all on their local computer. Let me show you how to get started in three easy steps.
1. Install Docker
SQL Server 2008 R2 Express is a free edition of SQL Server that is ideal for learning, developing and powering desktop, web and small server applications, and for redistribution by ISVs. Our site,SQL Server Tutorials,Microsoft MS SQL Server Management Studio (SSMS)-SQL Server 2016,download, 2012,2014,2017,mac,express,2008 R2,tutorial about. FOLLOW US Site Map.
The first step is to install Docker. Start at https://store.docker.com/editions/community/docker-ce-desktop-mac, and click the Get Docker button on the top right. That will download a disc image containing the application. Drag Docker.app into your Applications folder and give it a double-click to launch. Look for the Docker icon in the top menu bar. When the animation stops, Docker is ready to go. Step one: done.
2. Pull the SQL Server 2017 container
Next, start up Terminal.app. This is where you'll issue commands to Docker. Microsoft provides pre-configured images that include the Developer edition of SQL Server 2017 running on Ubuntu Linux. You can pull the most recent version with the following command.
After supplying your MacOS Administrator password, the image is downloaded.
Docker images need to be unpacked into containers, and a single image can be used to create as many identical containers as you'd like; just be sure to give them unique names. The following command will create a single container called 'sqlserver1' from the image you just downloaded. A couple of points:
- Note that you'll want to provide your own strong password for the SQL Server System Administrator account. Just replace 'YourStrong!Passw0rd' with something better.
- Port 1401 on the local computer will be forwarded to SQL Server's default listening port of 1433 inside the container. This will be important to remember later.
- Make sure that you forward a different port to 1433 if you decide to create additional containers.
To verify that everything is working as intended, you can check the status of Docker's containers.
You should see a line for the container and, hopefully, a status of 'up.' If you see 'exited' here, go back and double check the previous commands were typed correctly. You can also try 'docker stop sqlserver1' followed by 'docker start sqlserver1' to reset the server. With the container now running, you're done with step two.
3. Install SQL Operations Studio
Microsoft is in the beginning stages of developing a cross-platform graphical user interface for SQL Server called SQL Operations Studio. Though it's still in an early public preview, SQL Ops Studio is already showing promise as a robust, lightweight interface that brings the best of SQL Server Management Studio (a venerable workhorse, but sadly Windows-only) over to the Mac and Linux platforms. The Ops Studio GitHub page will be your source of information as the project progresses. Head over to the GitHub repository, scroll down to the first section of the readme and download the MacOS zip containing the latest stable preview.
Upon Operations Studio's first launch, the Connection window will automatically prompt you for login credentials. Use 'localhost' as the name of the server, 'SA' as the user name, and fill in the password that you established when the Docker container was created. Then press the Advanced button, and scroll through the properties list until you get to the General section. Fill in the port number of 1401 here, or whichever port you're passing to SQL Server's 1433 listening port. Press OK, then Connect.
That should connect, and pass you back to the main interface. If you've ever seen Visual Studio Code, then you'll instantly recognize the interface's clean and well-organized layout. On the left is a listing of servers you're connected to. Expand the server folder to explore databases, security items and so on.
You're now up and running with the SQL Server database engine running in a Docker container, and you can manage it with Operations Studio on your Mac!
Bonus step 4. Start working with your new SQL Database Engine
What good is a server without a database? Right-click the Databases folder, and choose New Query. In the SQLQuery1 tab, type in the following command.
Press the Run button to create your first database, which you should see pop up under the Databases folder. You might need to right-click the databases folder and choose Refresh if it doesn't show up immediately.
Operations Studio has a great feature called Snippets that help you quickly write common T-SQL commands. Clear out the CREATE DATABASE statement and change the Connection drop-down at the top to MyDatabase. Type 'sql' to see the list of included snippets presented in the IntelliSense popup box.
Sql Express 2017 Advanced Download
Arrow down to sqlCreateTable and press Return. Operations Studio fills in all of the T-SQL to help you create a table in the database.
Notice that all of the TableName placeholders are selected, ready for you to overwrite them with your own name. Type it once, and each one gets updated simultaneously. Press the tab key to move over to SchemaName and change that to 'dbo' (since we haven't created any other schemas at this point). Then all that's left is to modify the Column1 and Column2 placeholders on lines 10 and 11, choose appropriate data types, and add additional columns as needed.
Press the Run button when done to create your first table, in your first database, on your SQL Server instance, running on Ubuntu Linux, inside of a Docker container, on your Mac.
You're done!
Welcome from SQL Server 2017: Linux, Docker, and macOS by Adam Wilbert
','resolvedBy':'manual','resolved':true}'>Welcome from SQL Server 2017: Linux, Docker, and macOS by Adam Wilbert
Dig in deeper with my course SQL Server 2017: Linux, Docker, and MacOS
I go into way more detail on the process of working with SQL Server on these newly available platforms in my newest course here on LinkedIn Learning. In it, I demonstrate the process of setting up SQL Server on Linux, use the sqlcmd command line tool, dive deeper into Docker, and connect instances to and from other machines on the network. Or, for more information on how to use SQL Server now that you're up and running, check out Learn SQL Server 2017.
Adam Wilbert is a LinkedIn Learning / Lynda.com author of over forty courses on SQL Server, Microsoft Access, database design and development, and mapping with ArcGIS. Come say 'hi' on Twitter: @awilbert.
Prerequisites
- Microsoft SQL Server 2017 (Express Edition) – download link from the Microsoft site
- Microsoft SQL Server Management Studio 18.2 - download link from the Microsoft site
- DataGrip 2019.1 and later – download link from the JetBrains site
Step 1. Configure the SQL Server Configuration Manager
To open SQL Server Configuration Manager, open the Search dialog on Windows and type
SQLServerManager14.msc
(for Microsoft SQL Server 2017). Double-click the found result. If you use other versions of Microsoft SQL Server, change the second digit before .msc
:SQLServerManager13.msc
for SQL Server 2016SQLServerManager12.msc
for SQL Server 2014SQLServerManager11.msc
for SQL Server 2012
Run the SQL Server Browser
SQL Server Browser listens for incoming requests and provides information about Microsoft SQL Server instances on the computer. For more information about SQL Server Browser, see SQL Server Browser in the Microsoft documentation.
If the SQL Server Browser menu items are disabled, try to enable the SQL Server Agent service.
- In the SQL Server Configuration Manager, click SQL Server Services.
- In the right pane that lists server services, right-click SQL Server Browser and select Start.
Enable SQL Server Agent
If the SQL Server Browser is running, you can skip this procedure.
SQL Server Agent is a Microsoft Windows service that executes scheduled administrative tasks. For more information about the service, see SQL Server Agent in the official Microsoft documentation. Ensure that SQL Server Agent is running and starts automatically. After the change, a restart might be required.
- Navigate to Control Panel | Administrative Tools | Services.
- In the Services window, right-click SQL Server Agent(<server_name>) and select Properties. For this tutorial, <server_name> is MSSQLSERVER.
- From the Startup type list, select Automatic and click Start.
Enable the TCP/IP connection
- In the SQL Server Configuration Manager, expand SQL Server Configuration and click Protocols for MSSQLSERVER, where MSSQLSERVER is a name of the Microsoft SQL Server instance.
- In the list of protocol names, right-click TCP/IP and select Properties.
- On the Protocol tab, from the Enabled list, select Yes.
- On the IP Addresses tab, find the interface that your workstation uses and see the connection port. By default, the port is 1433. Verify that other running applications do not use the same port.
If you changed any settings, restart the server. For most situations, the restart resolves connection problems.
Step 2. Configure SQL Server Management Studio (SSMS)
Create a user
- In the SQL Server Management Studio (SSMS), navigate to Security | Logins.
- Right-click the Logins root folder and select New Login.
- On the General page, specify a login name in the Login name field.
- Select authentication mode. You can select between the following authentication modes:
- Windows authentication: to use your domain login and password.
- SQL Server authentication: to use a custom login and password. If you select Enforce password security policy checkbox, the user must change the assigned password before connecting to Microsoft SQL Server with DataGrip. Otherwise, clear the Enforce password security policy checkbox.
- Click OK.
Configure user roles
- Right-click the created user profile and select Properties.
- On the Server Roles page, select the appropriate user role (for example, sysadmin).
![Sql server 2017 developer edition Sql server 2017 developer edition](/uploads/1/2/9/3/129309590/482396279.jpg)
Step 3. Connect to Microsoft SQL Server with DataGrip
The following section describes configuration of DataGrip on Windows, macOS, and Linux. Note that the Use Windows domain authentication checkbox is available only on Windows. To configure Windows domain authentication on macOS and Linux, see Connect by using Windows domain authentication.
Windows
Connect by using SQL Server authentication
- Navigate to File | Data Sources or press Ctrl+Alt+Shift+S.
- In the Data Sources and Drivers dialog, click the Add icon () and select Microsoft SQL Server.
- Click the Driver link and select Microsoft SQL Server (jTds).
- At the bottom of the data source settings area, click the Download missing driver files link. Alternatively, you can specify user drivers for the data source. For more information about user drivers, see Add a user driver to an existing connection.
- In Host, Instance, and Port fields, specify your connection details.
- From the Authentication list, select User & Password.
- In User and Password fields, specify your credentials.
- To ensure that the connection to the data source is successful, click Test Connection.
Connect by using single sign-on for Microsoft SQL Server
If you run DataGrip on Windows in the same domain as the Microsoft SQL Server database, you can use the Single-Sign On (SSO).
- Navigate to File | Data Sources or press Ctrl+Alt+Shift+S.
- In the Data Sources and Drivers dialog, click the Add icon () and select Microsoft SQL Server.
- Click the Driver link and select Microsoft SQL Server (jTds).
- At the bottom of the data source settings area, click the Download missing driver files link. Alternatively, you can specify user drivers for the data source. For more information about user drivers, see Add a user driver to an existing connection.
- From the Authentication list, select Windows credentials.
- To ensure that the connection to the data source is successful, click Test Connection.
Connect by using Windows domain authentication
- Navigate to File | Data Sources or press Ctrl+Alt+Shift+S.
- In the Data Sources and Drivers dialog, click the Add icon () and select Microsoft SQL Server.
- Click the Driver link and select Microsoft SQL Server (jTds).
- At the bottom of the data source settings area, click the Download missing driver files link. Alternatively, you can specify user drivers for the data source. For more information about user drivers, see Add a user driver to an existing connection.
- In Host, Instance, and Port fields, specify your connection details.
- From the Authentication list, select Domain credentials.
- In the Domain field, specify the domain (for example,
DEVELOPMENT
). - In User and Password fields, specify your domain credentials. In the User field, type your domain user without the domain prefix (for example,
John.Smith
instead ofDOMAINJohn.Smith
).Alternatively, on the General tab, specify the connection string. Consider the following example of a full connection string:jdbc:jtds:sqlserver://UNIT-670:1433;domain=DEVELOPMENT;instance=MSSQLSERVER;databaseName=guest; - To ensure that the connection to the data source is successful, click Test Connection.
macOS and Linux
Connect by using SQL Server authentication
- Navigate to File | Data Sources or press ⌘;.
- In the Data Sources and Drivers dialog, click the Add icon ( ) and select Microsoft SQL Server.
- Click the Driver link and select Microsoft SQL Server (jTds).
- At the bottom of the data source settings area, click the Download missing driver files link. Alternatively, you can specify user drivers for the data source. For more information about user drivers, see Add a user driver to an existing connection.
- In Host, Instance, and Port fields, specify your connection details.
- From the Authentication list, select User & Password.
- In User and Password fields, specify your credentials.
- To ensure that the connection to the data source is successful, click Test Connection.
Connect by using Windows domain authentication
Sql Server Management Studio Express 2017
- Navigate to File | Data Sources or press ⌘;.
- In the Data Sources and Drivers dialog, click the Add icon ( ) and select Microsoft SQL Server.
- Click the Driver link and select Microsoft SQL Server (jTds).
- At the bottom of the data source settings area, click the Download missing driver files link. Alternatively, you can specify user drivers for the data source. For more information about user drivers, see Add a user driver to an existing connection.
- In Host, Instance, and Port fields, specify your connection details.
- From the Authentication list, select Domain credentials.
- In the Domain field, specify the domain (for example,
DEVELOPMENT
). - In User and Password fields, specify your domain credentials. In the User field, type your domain user without the domain prefix (for example,
John.Smith
instead ofDOMAINJohn.Smith
).Alternatively, on the General tab, specify the connection string. Consider the following example of a full connection string:jdbc:jtds:sqlserver://UNIT-670:1433;domain=DEVELOPMENT;instance=MSSQLSERVER;databaseName=guest; - To ensure that the connection to the data source is successful, click Test Connection.