Release notes for SQL Server 2017 on Linux
Applies to: SQL Server 2017 (14.x) - Linux
The following release notes apply to SQL Server 2017 (14.x) running on Linux. This article is broken into sections for each release. Detailed supportability and known issues are listed at the end of the article. Each release has a link to a support article describing the changes as well as links to the Linux package downloads.
These release notes are specifically for SQL Server 2017 (14.x) releases. For release notes on other editions, see the following articles:
|Platform||File System||Installation Guide|
|Red Hat Enterprise Linux 7.7 - 7.9, or 8.0 - 8.6 Server||XFS or EXT4||Installation guide|
|SUSE Enterprise Linux Server v12 SP3 - SP5||XFS or EXT4||Installation guide|
|Ubuntu 16.04 LTS 1, 18.04 LTS||XFS or EXT4||Installation guide|
|Docker Engine 1.8+ on Linux||N/A||Installation guide|
1 Support for SQL Server on Ubuntu 16.04 is limited. At the end of April 2021, Ubuntu 16.04 transitioned from its standard five-year maintenance window for long term support (LTS) releases, into extended security maintenance (ESM) support. For more details, see Ubuntu 16.04 LTS transitions to Extended Security Maintenance (ESM) | Ubuntu.
Most existing client tools that target SQL Server can seamlessly target SQL Server running on Linux. Some tools might have a specific version requirement to work well with Linux. For a full list of SQL Server tools, see SQL Tools and Utilities for SQL Server.
Latest versions for all packages
This section lists the latest versions of each package per distribution, for SQL Server 2017. The following table shows the most recent release, which is CU 31. For full release history, see Release history for SQL Server 2017.
|SQL Server 2017 (14.x)||CU 31||2022-09-20||14.0.3456.2||KB 5016884|
This is the final cumulative update for SQL Server 2017 (14.x).
- As of CU 4, SQL Server Agent is no longer installed as a separate package. It is installed with the Database Engine package and must be enabled to use.
- The mssql-server-is package isn't supported on SUSE in this release. See SQL Server Integration Services (SSIS) for more information.
|Distribution||Package name||Package version||Download|
|Red Hat Enterprise Linux|
|RHEL 8||Database Engine||14.0.3456.2-3||Database Engine RPM package|
|RHEL 8||Full-Text Search||14.0.3456.2-3||Full-Text Search RPM package|
|RHEL 8||High Availability||14.0.3456.2-3||High Availability RPM package|
|RHEL 7||SSIS||14.0.3015.40-1||SSIS RPM package|
|SUSE Enterprise Linux Server|
|SLES 12||Database Engine||14.0.3456.2-3||Database Engine RPM package|
|SLES 12||Full-Text Search||14.0.3456.2-3||Full-Text Search RPM package|
|SLES 12||High Availability||14.0.3456.2-3||High Availability RPM package|
|Ubuntu 18.04||Database Engine||14.0.3456.2-3||Database Engine Debian package|
|Ubuntu 18.04||Full-Text Search||14.0.3456.2-3||Full-Text Search Debian package|
|Ubuntu 18.04||High Availability||14.0.3456.2-3||High Availability Debian package|
|Ubuntu 16.04||SSIS||14.0.3015.40-1||SSIS Debian package|
How to install updates
If you have configured the CU repository (
mssql-server-2017), then you will get the latest CU of SQL Server packages when you perform new installations. If you require Docker container images, see official images for Microsoft SQL Server on Linux for Docker Engine. For more information about repository configuration, see Configure repositories for SQL Server on Linux.
If you are updating existing SQL Server packages, run the appropriate update command for each package to get the latest CU. For specific update instructions for each package, see the following installation guides:
- Install SQL Server package
- Install Full-Text Search package
- Install SQL Server Integration Services
- Enable SQL Server Agent
The following table lists the release history for SQL Server 2017 (14.x).
|CU 29 GDR||14.0.3445.2||2022-06-14|
|CU 22 GDR||14.0.3370.1||2021-01-12|
|CU 15 GDR||14.0.3192.2||2019-07-09|
|CU 9 GDR||14.0.3035.2||2018-08-18|
The following sections describe known issues with SQL Server 2017 (14.x) on Linux.
The length of the hostname where SQL Server is installed needs to be 15 characters or less.
- Resolution: Change the name in
/etc/hostnameto something 15 characters long or less.
- Resolution: Change the name in
Manually setting the system time backwards in time will cause SQL Server to stop updating the internal system time within SQL Server.
- Resolution: Restart SQL Server.
Only single instance installations are supported.
- Resolution: If you want to have more than one instance on a given host, consider using VMs or Docker containers.
SQL Server Configuration Manager can't connect to SQL Server on Linux.
The default language of the sa login is English.
- Resolution: Change the language of the sa login with the
- Resolution: Change the language of the sa login with the
masterdatabase can't be moved with the mssql-conf utility. Other system databases can be moved with mssql-conf.
When restoring a database that was backed up on SQL Server on Windows, you must use the
WITH MOVEclause in the Transact-SQL statement.
Certain algorithms (cipher suites) for Transport Layer Security (TLS) don't work properly with SQL Server on Linux. This results in connection failures when attempting to connect to SQL Server, and problems establishing connections between replicas in high availability groups.
Resolution: Modify the
mssql.confconfiguration script for SQL Server on Linux to disable problematic cipher suites, by doing the following:
Add the following to
In the preceding code,
!negates the expression. This tells OpenSSL to not use the following cipher suite.
Restart SQL Server with the following command.
sudo systemctl restart mssql-server
SQL Server 2014 (12.x) databases on Windows that use In-memory OLTP can't be restored to SQL Server on Linux. To restore a SQL Server 2014 (12.x) database that uses In-memory OLTP, first upgrade the databases to a newer version of SQL Server on Windows, before moving them to SQL Server on Linux, via backup/restore or detach/attach.
ADMINISTER BULK OPERATIONSis not supported on Linux at this time.
Features that involve outbound TCP connections from the
sqlservr process, such as linked servers or availability groups, might not work if both the following conditions are met:
The target server is specified as a hostname and not an IP address.
The source instance has IPv6 disabled in the kernel. To verify if your system has IPv6 enabled in the kernel, all the following tests must pass:
cat /proc/cmdlinewill print the boot cmdline of the current kernel. The output must not contain
/proc/sys/net/ipv6/directory must exist.
- A C program that calls
socket(AF_INET6, SOCK_STREAM, IPPROTO_IP)should succeed - the syscall must return an
fd != -1and not fail with
The exact error depends on the feature. For linked servers, this manifests as a login timeout error. For availability groups, the
ALTER AVAILABILITY GROUP JOIN DDL on the secondary will fail after 5 minutes with a
download configuration timeout error.
To work around this issue, do one of the following:
Use IPs instead of host names to specify the target of the TCP connection.
Enable IPv6 in the kernel by removing
ipv6.disable=1from the boot command line. The way to do this depends on the Linux distribution and the bootloader, such as grub. If you want IPv6 to be disabled, you can still disable it by setting
net.ipv6.conf.all.disable_ipv6 = 1in the
sysctlconfiguration (for example,
/etc/sysctl.conf). This will still prevent the system's network adapter from getting an IPv6 address, but allow the
sqlservrfeatures to work.
Network File System (NFS)
If you use Network File System (NFS) remote shares in production, note the following support requirements:
Use NFS version 4.2 or higher. Older versions of NFS don't support required features, such as
fallocateand sparse file creation, common to modern file systems.
Locate only the
/var/opt/mssqldirectories on the NFS mount. Other files, such as the SQL Server system binaries, aren't supported.
Ensure that NFS clients use the
nolockoption when mounting the remote share.
If your locale isn't English (
en_us) during setup, you must use UTF-8 encoding in your bash session/terminal. If you use ASCII encoding, you might see an error similar to the following:
UnicodeEncodeError: 'ascii' codec can't encode character u'\xf1' in position 8: ordinal not in range(128)
If you can't use UTF-8 encoding, run setup using the
MSSQL_LCIDenvironment variable to specify your language choice.
sudo MSSQL_LCID=<LcidValue> /opt/mssql/bin/mssql-conf setup
mssql-conf setup, and performing a non-English installation of SQL Server, incorrect extended characters are displayed after the localized text, "Configuring SQL Server...". Or, for non-Latin based installations, the sentence might be missing completely. The missing sentence should display the following localized string:
The licensing PID was successfully processed. The new edition is [<Name> edition].
This string is output for information purposes only, and the next SQL Server Cumulative Update will address this for all languages. This doesn't affect the successful installation of SQL Server in any way.
Not all filters are available with this release, including filters for Microsoft Office documents. For a list of supported filters, see Install SQL Server Full-Text Search on Linux.
SQL Server Integration Services (SSIS)
The mssql-server-is package isn't supported on SUSE in this release. It's currently supported on Ubuntu and on Red Hat Enterprise Linux (RHEL).
Integration Services packages can use ODBC connections on Linux. This functionality has been tested with the SQL Server and the MySQL ODBC drivers, but is also expected to work with any Unicode ODBC driver that observes the ODBC specification. At design time, you can provide either a DSN or a connection string to connect to the ODBC data; you can also use Windows authentication. For more info, see the blog post announcing ODBC support on Linux.
The following features aren't supported in this release when you run SSIS packages on Linux:
- Integration Services Catalog database
- Scheduled package execution by SQL Agent
- Windows Authentication
- Third-party components
- Change Data Capture (CDC)
- Integration Services Scale Out
- Azure Feature Pack for SSIS
- Hadoop and HDFS support
- Microsoft Connector for SAP BW
For a list of built-in SSIS components that aren't currently supported, or that are supported with limitations, see Limitations and known issues for SSIS on Linux.
For more info about SSIS on Linux, see the following articles:
- Blog post announcing SSIS support for Linux.
- Install SQL Server Integration Services (SSIS) on Linux
- Extract, transform, and load data on Linux with SSIS
SQL Server Management Studio (SSMS)
The following limitations apply to SQL Server Management Studio on Windows connected to SQL Server on Linux.
Maintenance plans aren't supported.
Management Data Warehouse (MDW) and the data collector in SQL Server Management Studio aren't supported.
SQL Server Management Studio UI components that have Windows Authentication or Windows event log options don't work with Linux. You can still use these features with other options, such as SQL logins.
Number of log files to retain can't be modified.
Submit and view feedback for