Quickstart: Install SQL Server and create a database on SUSE Linux Enterprise Server
Applies to:
SQL Server - Linux
In this quickstart, you install SQL Server 2017 (14.x) on SUSE Linux Enterprise Server (SLES) v12. Then you can connect with sqlcmd to create your first database and run queries.
For more information on supported platforms, see Release notes for SQL Server 2017 on Linux.
In this quickstart, you install SQL Server 2019 (15.x) on SUSE Linux Enterprise Server (SLES) v15 (SP3). Then you can connect with sqlcmd to create your first database and run queries.
For more information on supported platforms, see Release notes for SQL Server 2019 on Linux.
In this quickstart, you install SQL Server 2022 (16.x) on SUSE Linux Enterprise Server (SLES) v15 (SP3). Then you can connect with sqlcmd to create your first database and run queries.
For more information on supported platforms, see Release notes for SQL Server 2022 on Linux.
Tip
This tutorial requires user input and an internet connection. If you are interested in the unattended or offline installation procedures, see Installation guidance for SQL Server on Linux.
Prerequisites
You must have a SLES v12 SP5 machine with at least 2 GB of memory. The file system must be XFS or EXT4. Other file systems, such as BTRFS, are unsupported.
You must have a SLES v15 (SP1 - SP4) machine with at least 2 GB of memory. The file system must be XFS or EXT4. Other file systems, such as BTRFS, are unsupported.
You must have a SLES v15 (SP1 - SP4) machine with at least 2 GB of memory. The file system must be XFS or EXT4. Other file systems, such as BTRFS, are unsupported.
To install SUSE Linux Enterprise Server on your own machine, go to https://www.suse.com/products/server. You can also create SLES virtual machines in Azure. See Create and Manage Linux VMs with the Azure CLI, and use --image SLES
in the call to az vm create
.
If you've previously installed a community technology preview (CTP) or release candidate (RC) of SQL Server, you must first remove the old repository before following these steps. For more information, see Configure Linux repositories for SQL Server.
Note
At this time, the Windows Subsystem for Linux for Windows 10 or Windows 11 is not supported as an installation target.
For other system requirements, see System requirements for SQL Server on Linux.
Install SQL Server
To configure SQL Server on SLES, run the following commands in a terminal to install the mssql-server package:
Download the SQL Server 2017 (14.x) SLES repository configuration file:
sudo zypper addrepo -fc https://packages.microsoft.com/config/sles/12/mssql-server-2017.repo
Tip
If you want to install a different version of SQL Server, see the SQL Server 2019 (15.x) or SQL Server 2022 (16.x) version of this article.
Refresh your repositories.
sudo zypper --gpg-auto-import-keys refresh
To ensure that the Microsoft package signing key is installed on your system, you can import it using the command below:
sudo rpm --import https://packages.microsoft.com/keys/microsoft.asc
Before you install SQL Server, and after you have registered and activated your SUSE Linux Enterprise Server with SUSE Customer Center, you must activate both the Desktop Applications module and Development Tools module. These modules are required for some of the SQL Server package dependencies.
Now, you are ready to install SQL Server. Run the following commands to install SQL Server:
sudo zypper install -y mssql-server
After the package installation finishes, run
mssql-conf setup
and follow the prompts to set the SA password and choose your edition. As a reminder, the following SQL Server editions are freely licensed: Evaluation, Developer, and Express.sudo /opt/mssql/bin/mssql-conf setup
Remember to specify a strong password for the SA account. You need a minimum length 8 characters, including uppercase and lowercase letters, base-10 digits and/or non-alphanumeric symbols.
Once the configuration is done, verify that the service is running:
systemctl status mssql-server
If you plan to connect remotely, you might also need to open the SQL Server TCP port (default 1433) on your firewall. If you're using the SuSE firewall, you need to edit the
/etc/sysconfig/SuSEfirewall2
configuration file. Modify theFW_SERVICES_EXT_TCP
entry to include the SQL Server port number.FW_SERVICES_EXT_TCP="1433"
At this point, SQL Server is running on your SLES machine and is ready to use!
Download the SQL Server 2019 (15.x) SLES repository configuration file:
sudo zypper addrepo -fc https://packages.microsoft.com/config/sles/15/mssql-server-2019.repo
Warning
SUSE Linux Enterprise Server (SLES) is not a supported platform for the Community Technology Preview (CTP) 2.1 release of SQL Server 2022 (16.x). You won't be able to install SQL Server 2022 (16.x).
Tip
If you want to install a different version of SQL Server, see the SQL Server 2017 (14.x) or SQL Server 2022 (16.x) version of this article.
Refresh your repositories.
sudo zypper --gpg-auto-import-keys refresh
To ensure that the Microsoft package signing key is installed on your system, you can import it using the command below:
sudo rpm --import https://packages.microsoft.com/keys/microsoft.asc
Before you install SQL Server, and after you have registered and activated your SUSE Linux Enterprise Server with SUSE Customer Center, you must activate both the Desktop Applications module and Development Tools module. These modules are required for some of the SQL Server package dependencies.
Now, you are ready to install SQL Server. Run the following commands to install SQL Server:
sudo zypper install -y mssql-server
After the package installation finishes, run
mssql-conf setup
and follow the prompts to set the SA password and choose your edition. As a reminder, the following SQL Server editions are freely licensed: Evaluation, Developer, and Express.sudo /opt/mssql/bin/mssql-conf setup
Remember to specify a strong password for the SA account. You need a minimum length 8 characters, including uppercase and lowercase letters, base-10 digits and/or non-alphanumeric symbols.
Once the configuration is done, verify that the service is running:
systemctl status mssql-server
If you plan to connect remotely, you might need to open the SQL Server TCP port (default 1433) on your firewall.
Note
On SLES, you can manage your firewall using
firewalld
for example. Install it usingsudo zypper install firewalld
, and then start it up withsudo systemctl start firewalld
. Add the firewall rule withsudo firewall-cmd --zone=public --add-port=1433/tcp --permanent
, and then reload the firewall withsudo firewall-cmd --reload
for the settings to take effect.
At this point, SQL Server is running on your SLES machine and is ready to use!
Download the SQL Server 2022 (16.x) SLES repository configuration file:
sudo zypper addrepo -fc https://packages.microsoft.com/config/sles/15/mssql-server-2022.repo
Tip
If you want to install a different version of SQL Server, see the SQL Server 2017 (14.x) or SQL Server 2019 (15.x) version of this article.
Refresh your repositories.
sudo zypper --gpg-auto-import-keys refresh
To ensure that the Microsoft package signing key is installed on your system, you can import it using the command below:
sudo rpm --import https://packages.microsoft.com/keys/microsoft.asc
Before you install SQL Server, and after you have registered and activated your SUSE Linux Enterprise Server with SUSE Customer Center, you must activate both the Desktop Applications module and Development Tools module. These modules are required for some of the SQL Server package dependencies.
Now, you are ready to install SQL Server. Run the following commands to install SQL Server:
sudo zypper install -y mssql-server
After the package installation finishes, run
mssql-conf setup
and follow the prompts to set the SA password and choose your edition. As a reminder, the following SQL Server editions are freely licensed: Evaluation, Developer, and Express.sudo /opt/mssql/bin/mssql-conf setup
Remember to specify a strong password for the SA account. You need a minimum length 8 characters, including uppercase and lowercase letters, base-10 digits and/or non-alphanumeric symbols.
Once the configuration is done, verify that the service is running:
systemctl status mssql-server
If you plan to connect remotely, you might need to open the SQL Server TCP port (default 1433) on your firewall.
Note
On SLES, you can manage your firewall using
firewalld
for example. Install it usingsudo zypper install firewalld
, and then start it up withsudo systemctl start firewalld
. Add the firewall rule withsudo firewall-cmd --zone=public --add-port=1433/tcp --permanent
, and then reload the firewall withsudo firewall-cmd --reload
for the settings to take effect.
At this point, SQL Server is running on your SLES machine and is ready to use!
Install the SQL Server command-line tools
To create a database, you need to connect with a tool that can run Transact-SQL statements on SQL Server. The following steps install the SQL Server command-line tools: sqlcmd and bcp.
Add the SQL Server repository to Zypper.
sudo zypper addrepo -fc https://packages.microsoft.com/config/sles/15/prod.repo sudo zypper --gpg-auto-import-keys refresh
Install
mssql-tools
with the unixODBC developer package. For more information, see Install the Microsoft ODBC driver for SQL Server (Linux).sudo zypper install -y mssql-tools unixODBC-devel
For convenience, add
/opt/mssql-tools/bin/
to yourPATH
environment variable, to make sqlcmd or bcp accessible from the bash shell.For interactive sessions, modify the
PATH
environment variable in your~/.bash_profile
file with the following command:echo 'export PATH="$PATH:/opt/mssql-tools/bin"' >> ~/.bash_profile
For non-interactive sessions, modify the
PATH
environment variable in your~/.bashrc
file with the following command:echo 'export PATH="$PATH:/opt/mssql-tools/bin"' >> ~/.bashrc source ~/.bashrc
Connect locally
The following steps use sqlcmd to locally connect to your new SQL Server instance.
Run sqlcmd with parameters for your SQL Server name (
-S
), the user name (-U
), and the password (-P
). In this tutorial, you are connecting locally, so the server name islocalhost
. The user name issa
and the password is the one you provided for the SA account during setup.sqlcmd -S localhost -U sa -P '<YourPassword>'
You can omit the password on the command line to be prompted to enter it.
If you later decide to connect remotely, specify the machine name or IP address for the
-S
parameter, and make sure port 1433 is open on your firewall.If successful, you should get to a sqlcmd command prompt:
1>
.If you get a connection failure, first attempt to diagnose the problem from the error message. Then review the connection troubleshooting recommendations.
Create and query data
The following sections walk you through using sqlcmd to create a new database, add data, and run a simple query.
For more information about writing Transact-SQL statements and queries, see Tutorial: Writing Transact-SQL Statements.
Create a new database
The following steps create a new database named TestDB
.
From the sqlcmd command prompt, paste the following Transact-SQL command to create a test database:
CREATE DATABASE TestDB;
On the next line, write a query to return the name of all of the databases on your server:
SELECT Name from sys.databases;
The previous two commands were not executed immediately. You must type
GO
on a new line to execute the previous commands:GO
Insert data
Next create a new table, dbo.Inventory
, and insert two new rows.
From the sqlcmd command prompt, switch context to the new
TestDB
database:USE TestDB;
Create new table named
dbo.Inventory
:CREATE TABLE dbo.Inventory ( id INT, name NVARCHAR(50), quantity INT );
Insert data into the new table:
INSERT INTO dbo.Inventory VALUES (1, 'banana', 150); INSERT INTO dbo.Inventory VALUES (2, 'orange', 154);
Type
GO
to execute the previous commands:GO
Select data
Now, run a query to return data from the dbo.Inventory
table.
From the sqlcmd command prompt, enter a query that returns rows from the
dbo.Inventory
table where the quantity is greater than 152:SELECT * FROM dbo.Inventory WHERE quantity > 152;
Execute the command:
GO
Exit the sqlcmd command prompt
To end your sqlcmd session, type QUIT
:
QUIT
Performance best practices
After installing SQL Server on Linux, review the best practices for configuring Linux and SQL Server to improve performance for production scenarios. For more information, see Performance best practices and configuration guidelines for SQL Server on Linux.
Cross-platform data tools
In addition to sqlcmd, you can use the following cross-platform tools to manage SQL Server:
Tool | Description |
---|---|
Azure Data Studio | A cross-platform GUI database management utility. |
Visual Studio Code | A cross-platform GUI code editor that run Transact-SQL statements with the mssql extension. |
PowerShell Core | A cross-platform automation and configuration tool based on cmdlets. |
mssql-cli | A cross-platform command-line interface for running Transact-SQL commands. |
Connecting from Windows
SQL Server tools on Windows connect to SQL Server instances on Linux in the same way they would connect to any remote SQL Server instance.
If you have a Windows machine that can connect to your Linux machine, try the same steps in this topic from a Windows command-prompt running sqlcmd. You must use the target Linux machine name or IP address rather than localhost
, and make sure that TCP port 1433 is open on the SQL Server machine. If you have any problems connecting from Windows, see connection troubleshooting recommendations.
For other tools that run on Windows but connect to SQL Server on Linux, see:
Other deployment scenarios
For other installation scenarios, see the following resources:
- Upgrade: Learn how to upgrade an existing installation of SQL Server on Linux
- Uninstall: Uninstall SQL Server on Linux
- Unattended install: Learn how to script the installation without prompts
- Offline install: Learn how to manually download the packages for offline installation
For answers to frequently asked questions, see the SQL Server on Linux FAQ.
Next steps
Contribute to SQL documentation
Did you know that you can edit SQL content yourself? If you do so, not only do you help improve our documentation, but you also get credited as a contributor to the page.
For more information, see How to contribute to SQL Server documentation
Feedback
Submit and view feedback for