Edit

Release notes for SQL Server 2017 on Linux

  • Article

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. For detailed supportability and known issues, see Known issues. Each release links to a support article describing the changes, in addition 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:

Supported platforms

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.

Tip

For more information, review the system requirements for SQL Server on Linux. For the latest support policy for SQL Server, see the Technical support policy for Microsoft SQL Server.

Tools

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 GDR. For full release history, see Release history for SQL Server 2017.

Version Release Date Build KB article
SQL Server 2017 (14.x) CU 31 GDR 2023-02-14 14.0.3460.9 KB 5021126

Important

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. For more information, see SQL Server Integration Services (SSIS).
Distribution Package name Package version Download
Red Hat Enterprise Linux
RHEL 8 Database Engine 14.0.3460.9-3 Database Engine RPM package
RHEL 8 Full-Text Search 14.0.3460.9-3 Full-Text Search RPM package
RHEL 8 High Availability 14.0.3460.9-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.3460.9-3 Database Engine RPM package
SLES 12 Full-Text Search 14.0.3460.9-3 Full-Text Search RPM package
SLES 12 High Availability 14.0.3460.9-3 High Availability RPM package
Ubuntu
Ubuntu 18.04 Database Engine 14.0.3460.9-3 Database Engine Debian package
Ubuntu 18.04 Full-Text Search 14.0.3460.9-3 Full-Text Search Debian package
Ubuntu 18.04 High Availability 14.0.3460.9-3 High Availability Debian package
Ubuntu 16.04 SSIS 14.0.3015.40-1 SSIS Debian package

How to install updates

When you configure the CU repository (mssql-server-2017), you 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:

Release history

The following table lists the release history for SQL Server 2017 (14.x).

Release Version Release date
CU 31 GDR 14.0.3460.9 2023-02-14
CU 31 14.0.3456.2 2022-09-20
CU 30 14.0.3451.2 2022-07-13
CU 29 GDR 14.0.3445.2 2022-06-14
CU 29 14.0.3436.1 2022-03-30
CU 28 14.0.3430.2 2022-01-13
CU 27 14.0.3421.10 2021-10-27
CU 26 14.0.3411.3 2021-09-14
CU 25 14.0.3401.7 2021-07-12
CU 24 14.0.3391.2 2021-05-10
CU 23 14.0.3381.3 2021-02-24
CU 22 GDR 14.0.3370.1 2021-01-12
GDR 3 14.0.2037.2 2021-01-12
CU 22 14.0.3356.20 2020-09-10
CU 21 14.0.3335.7 2020-07-01
CU 20 14.0.3294.2 2020-04-10
CU 19 14.0.3281.6 2020-02-05
CU 18 14.0.3257.3 2019-12-09
CU 17 14.0.3238.1 2019-10-08
CU 16 14.0.3223.3 2019-08-01
CU 15 GDR 14.0.3192.2 2019-07-09
CU 15 14.0.3162.1 2019-05-23
CU 14 14.0.3076.1 2019-03-25
CU 13 14.0.3048.4 2018-12-18
CU 12 14.0.3045.24 2018-10-24
CU 11 14.0.3038.14 2018-09-20
CU 10 14.0.3037.1 2018-08-27
CU 9 GDR 14.0.3035.2 2018-08-18
GDR 2 14.0.2002.14 2018-08-18
CU 9 14.0.3030.27 2018-07-18
CU 8 14.0.3029.16 2018-06-21
CU 7 14.0.3026.27 2018-05-24
CU 6 14.0.3025.34 2018-04-19
CU 5 14.0.3023.8 2018-03-20
CU 4 14.0.3022.28 2018-02-20
CU 3 14.0.3015.40 2018-01-03
GDR 1 14.0.2000.63 2018-01-03
CU 2 14.0.3008.27 2017-11-28
CU 1 14.0.3006.16 2017-10-24
GA 14.0.1000.169 2017-10-02

Known issues

The following sections describe known issues with SQL Server 2017 (14.x) on Linux.

General

  • The length of the hostname where SQL Server is installed needs to be 15 characters or less.

    • Resolution: Change the name in /etc/hostname to something 15 characters long or less.

  • 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 ALTER LOGIN statement.

Databases

  • The master database 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 MOVE clause 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.conf configuration script for SQL Server on Linux to disable problematic cipher suites, by doing the following:

      1. Add the following to /var/opt/mssql/mssql.conf.

        [network]
tlsciphers=AES256-GCM-SHA384:AES128-GCM-SHA256:AES256-SHA256:AES128-SHA256:AES256-SHA:AES128-SHA:!ECDHE-RSA-AES128-GCM-SHA256:!ECDHE-RSA-AES256-GCM-SHA384:!ECDHE-ECDSA-AES256-GCM-SHA384:!ECDHE-ECDSA-AES128-GCM-SHA256:!ECDHE-ECDSA-AES256-SHA384:!ECDHE-ECDSA-AES128-SHA256:!ECDHE-ECDSA-AES256-SHA:!ECDHE-ECDSA-AES128-SHA:!ECDHE-RSA-AES256-SHA384:!ECDHE-RSA-AES128-SHA256:!ECDHE-RSA-AES256-SHA:!ECDHE-RSA-AES128-SHA:!DHE-RSA-AES256-GCM-SHA384:!DHE-RSA-AES128-GCM-SHA256:!DHE-RSA-AES256-SHA:!DHE-RSA-AES128-SHA:!DHE-DSS-AES256-SHA256:!DHE-DSS-AES128-SHA256:!DHE-DSS-AES256-SHA:!DHE-DSS-AES128-SHA:!DHE-DSS-DES-CBC3-SHA:!NULL-SHA256:!NULL-SHA

        Note

        In the preceding code, ! negates the expression. This tells OpenSSL to not use the following cipher suite.

      2. 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.

  • User permission ADMINISTER BULK OPERATIONS is not supported on Linux at this time.

Network

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:

  1. The target server is specified as a hostname and not an IP address.

  2. 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/cmdline will print the boot cmdline of the current kernel. The output must not contain ipv6.disable=1.
    • The /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 != -1 and not fail with EAFNOSUPPORT.

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:

  1. Use IPs instead of host names to specify the target of the TCP connection.

  2. Enable IPv6 in the kernel by removing ipv6.disable=1 from 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 = 1 in the sysctl configuration (for example, /etc/sysctl.conf). This will still prevent the system's network adapter from getting an IPv6 address, but allow the sqlservr features 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 fallocate and sparse file creation, common to modern file systems.

  • Locate only the /var/opt/mssql directories on the NFS mount. Other files, such as the SQL Server system binaries, aren't supported.

  • Ensure that NFS clients use the nolock option when mounting the remote share.

Localization

  • 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_LCID environment variable to specify your language choice.

    sudo MSSQL_LCID=<LcidValue> /opt/mssql/bin/mssql-conf setup

  • When running 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.

Full-Text Search

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:

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.

See also

Next steps