Release notes for SQL Server 2019 on Linux

• 10/01/2020
• 18 minutes to read
• • V
  • M
  • r
  • g
  • v
  • +2

THIS TOPIC APPLIES TO: SQL Server 2019 and later (Linux only) Azure SQL Database Azure Synapse Analytics Parallel Data Warehouse

The following release notes apply to SQL Server 2019 running on Linux. This article is broken into sections for each release. Each release has a link to a support article describing the CU changes as well as links to the Linux package downloads.

Supported platforms

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.

Release history

The following table lists the release history for SQL Server 2019 releases.

How to install updates

If you have configured the CU repository (mssql-server-2019), 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
• Install SQL Server 2019 Machine Learning Services R and Python support on Linux
• Install PolyBase package
• Enable SQL Server Agent

CU8-GDR (January 2021)

This is the Cumulative Update 8-GDR (CU8-GDR) release of SQL Server 2019 (15.x). The SQL Server Database Engine version for this release is 15.0.4083.2. For information about the fixes and improvements, see https://support.microsoft.com/help/4577194.

Package details

For manual or offline package installations, you can download the RPM and Debian packages with the information in the following table:

CU8 (September 2020)

This is the Cumulative Update 8 (CU8) release of SQL Server 2019 (15.x). The SQL Server Database Engine version for this release is 15.0.4073.23. For information about the fixes and improvements, see https://support.microsoft.com/help/4577194.

Package details

For manual or offline package installations, you can download the RPM and Debian packages with the information in the following table:

CU6 (July 2020)

This is the Cumulative Update 6 (CU6) release of SQL Server 2019 (15.x). The SQL Server Database Engine version for this release is 15.0.4053.23. For information about the fixes and improvements, see https://support.microsoft.com/help/4563110.

Package details

For manual or offline package installations, you can download the RPM and Debian packages with the information in the following table:

CU5 (June 2020)

This is the Cumulative Update 5 (CU5) release of SQL Server 2019 (15.x). The SQL Server Database Engine version for this release is 15.0.4043.16. For information about the fixes and improvements, see https://support.microsoft.com/help/4552255.

Package details

For manual or offline package installations, you can download the RPM and Debian packages with the information in the following table:

CU4 (April 2020)

This is the Cumulative Update 4 (CU4) release of SQL Server 2019 (15.x). The SQL Server Database Engine version for this release is 15.0.4033.1. For information about the fixes and improvements, see https://support.microsoft.com/help/4548597.

Package details

For manual or offline package installations, you can download the RPM and Debian packages with the information in the following table:

CU3 (March 2020)

This is the Cumulative Update 3 (CU3) release of SQL Server 2019 (15.x). The SQL Server Database Engine version for this release is 15.0.4023.6. For information about the fixes and improvements, see https://support.microsoft.com/help/4538853.

Package details

For manual or offline package installations, you can download the RPM and Debian packages with the information in the following table:

CU2 (February 2020)

This is the Cumulative Update 2 (CU2) release of SQL Server 2019 (15.x). The SQL Server Database Engine version for this release is 15.0.4013.40. For information about the fixes and improvements, see https://support.microsoft.com/help/4536075.

Package details

For manual or offline package installations, you can download the RPM and Debian packages with the information in the following table:

CU1 (January 2020)

This is the Cumulative Update 1 (CU1) release of SQL Server 2019 (15.x). The SQL Server Database Engine version for this release is 15.0.4003.23. For information about the fixes and improvements in this release, see https://support.microsoft.com/en-us/help/4527376.

Package details

For manual or offline package installations, you can download the RPM and Debian packages with the information in the following table:

GA (November 2019)

This is the General Availability (GA) release of SQL Server 2019 (15.x). The SQL Server Database Engine version for this release is 15.0.2000.5.

Package details

For manual or offline package installations, you can download the RPM and Debian packages with the information in the following table:

Release candidate (August 2019)

The following sections provide package locations and known issues for the release candidate. To learn more about new features for Linux on SQL Server 2019, see the What's new in SQL Server 2019.

Package details

For manual or offline package installations, you can download the RPM and Debian packages with the information in the following table:

Known issues

The following sections describe known issues with the General Availability (GA) release of SQL Server 2019 (15.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.

• OLEDB provider logs the following warning: Failed to verify the Authenticode signature of 'C:\binn\msoledbsql.dll'. Signature verification of SQL Server DLLs will be skipped. Genuine copies of SQL Server are signed. Failure to verify the Authenticode signature might indicate that this is not an authentic release of SQL Server. Install a genuine copy of SQL Server or contact customer support.

  • Resolution: No action is required. The OLEDB provider is signed using SHA256. SQL Server Database engine doesn't validate the signed .dll correctly.

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) do not work properly with SQL Server on Linux. This results in connection failures when attempting to connect to SQL Server, as well as 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 cannot be restored on SQL Server 2019 (15.x) on Linux. To restore a SQL Server 2014 (12.x) database that uses in-memory OLTP, first upgrade the databases to SQL Server 2016 (13.x), SQL Server 2017, or SQL Server 2019 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.

Networking

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 hostnames to specify the target of the TCP connection.

2. Enable IPv6 in the kernel by removing ipv6.disable=1 from the boot cmdline. The way to do this depends on the Linux distribution and the bootloader, such as grub. If you do 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 do not 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, are not supported.
• Ensure that NFS clients use the nolock option when mounting the remote share.

Localization

• If your locale is not 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 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 is not supported on SUSE in this release. It's currently supported on Ubuntu and on Red Hat Enterprise Linux (RHEL).

• With Integration Services on Linux CTP 2.1 Refresh and later, 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 are not 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.

Next steps

To get started, see the following quickstarts:

• Install on Red Hat Enterprise Linux
• Install on SUSE Linux Enterprise Server
• Install on Ubuntu
• Run on Docker
• Provision a SQL VM in Azure
• Run & Connect - Cloud

For answers to frequently asked questions, see the SQL Server on Linux FAQ.