| title | Release notes for SQL Server vNext on Linux | Microsoft Docs |
|---|---|
| description | This topic contains the release notes and supported features for SQL Server vNext running on Linux. Release notes are included for CTP 1.4 and prior versions. |
| author | rothja |
| ms.author | jroth |
| manager | jhubbard |
| ms.date | 03/15/2017 |
| ms.topic | article |
| ms.prod | sql-linux |
| ms.technology | database-engine |
| ms.assetid | 1314744f-fcaf-46db-800e-2918fa7e1b6c |
The following release notes apply to SQL Server vNext running on Linux. This release supports many of the SQL Server database engine features for Linux. The topic below is broken into sections for each release, beginning with the most recent release, CTP 1.4. See the information in the each section for supported platforms, tools, features, and known issues.
| Platform | File System | Installation Guide |
|---|---|---|
| Red Hat Enterprise Linux 7.3 Workstation, Server, and Desktop | XFS or EXT4 | Installation guide |
| SUSE Enterprise Linux Server v12 SP2 | EXT4 | Installation guide |
| Ubuntu 16.04LTS and 16.10 | EXT4 | Installation guide |
| Docker Engine 1.8+ on Windows, Mac, or Linux | N/A | Installation guide |
Note
You need at least 3.25GB of memory to run SQL Server on Linux. SQL Server Engine has been tested up to 1 TB of memory at this time.
The SQL Server engine version for this release is 14.0.304.138-1. Package details and download locations for the RPM and Debian packages are listed in the following table. Note that you do not need to download these packages directly if you use the steps in the installation guides.
| Package | Version | Downloads |
|---|---|---|
| Red Hat RPM package | 14.0.304.138-1 | Engine RPM package High Availability RPM package Full-text Search RPM package SQL Server Agent RPM package |
| SLES RPM package | 14.0.304.138-1 | mssql-server Engine RPM package High Availability RPM package Full-text Search RPM package SQL Server Agent RPM package |
| Ubuntu 16.04 Debian package | 14.0.304.138-1 | Engine Debian package High Availability Debian package Full-text Search Debian package SQL Server Agent Debian package |
| Ubuntu 16.10 Debian package | 14.0.304.138-1 | Engine Debian package High Availability Debian package Full-text Search Debian package SQL Server Agent Debian package |
| Tool | Minimum version |
|---|---|
| SQL Server Management Studio (SSMS) for Windows - Release Candidate 2 | 17.0 |
| SQL Server Data Tools for Visual Studio - Release Candidate 2 | 17.0 |
| Visual Studio Code with the mssql extension | Latest (0.2.1) |
Note
The SQL Server Management Studio and SQL Server Data Tools versions specified above are Release Candidates, hence not recommended for use in production.
The following features and services are not available on Linux at this time. The support of these features will be increasingly enabled during the monthly updates cadence of the preview program.
| Area | Unsupported feature or service |
|---|---|
| Database engine | Replication |
| Stretch DB | |
| Polybase | |
| Distributed Query | |
| System extended stored procedures (XP_CMDSHELL, etc.) | |
| Filetable | |
| CLR assemblies with the EXTERNAL_ACCESS or UNSAFE permission set | |
| High Availability | |
| Database mirroring | |
| Security | Active Directory Authentication |
| Windows Authentication | |
| Extensible Key Management | |
| Use of user-provided certificate for SSL or TLS | |
| Services | SQL Server Browser |
| SQL Server R services | |
| StreamInsight | |
| Analysis Services | |
| Reporting Services | |
| Integration Services | |
| Data Quality Services | |
| Master Data Services |
The following sections describe known issues with this release of SQL Server vNext CTP 1.4 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/hostname to something 15 characters long or less.
-
Do not run the command
ALTER SERVICE MASTER KEY REGENERATE. There is a known bug that will cause SQL Server to become unstable. If you need to regenerate the Service Master Key, you should back up your database files, uninstall and then re-install SQL Server, and then restore your database files again. -
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.
-
Some time zone names in Linux don’t map exactly to Windows time zone names.
- Resolution: Use time zone names from TZID column in the ‘Mapping for: Windows’ section table on the Unicode.org documentation page.
-
SQL Server Engine expects lines in text files to be terminated with CR-LF (Windows-style line formatting).
-
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.
-
All log files and error logs are encoded in UTF-16.
-
SQL Server Configuration Manager can’t connect to SQL Server on Linux.
-
CREATE ASSEMBLY will not work when trying to use a file. Use the FROM method instead for now.
-
Changing the locations of TempDB data and log files is not supported.
-
System databases can not be moved with the mssql-conf utility.
-
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.
-
Distributed transactions requiring the Microsoft Distributed Transaction Coordinator service are not supported on SQL Server running on Linux. SQL Server to SQL Server distributed transactions are supported.
-
Always On Availability Groups in Linux may be subject to data loss if replicas are in synchronous commit mode. See Configure Always On Availability Group for SQL Server on Linux.
-
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.
-
The Korean word breaker takes several seconds to load and generates an error on first use. After this initial error, it should work normally.
- In-Memory OLTP databases can only be created in the /var/opt/mssql directory. For more information, visit the In-memory OLTP Topic.
-
Using SqlPackage requires specifying an absolute path for files. Using relative paths will map the files under the“/tmp/sqlpackage.<code>/system/system32” folder.
- Resolution: Use absolute file paths.
-
SqlPackage shows the location of files with a “C:\” prefix.
-
SQL Server Command Line tools (mssql-tools) and the ODBC Driver (msodbcsql) depends on a custom unixODBC Driver Manager. This causes conflicts if you have a previously installed unixODBC Driver Manager.
- Resolution: On Ubuntu, the conflict will be resolved automatically. When prompted if you would like to unisntall the existing unixODBC Driver Manager, type 'y' and proceed with the installation. On RedHat, you will have to remove the existing unixODBC Driver Manager manually using
yum remove unixODBC. We are working on fixing this limitation for RHEL and SUSE and should have an update for you soon.
- Resolution: On Ubuntu, the conflict will be resolved automatically. When prompted if you would like to unisntall the existing unixODBC Driver Manager, type 'y' and proceed with the installation. On RedHat, you will have to remove the existing unixODBC Driver Manager manually using
The following limitations apply to SSMS on Windows connected to SQL Server on Linux.
-
Maintenance plans are not supported.
-
Management Data Warehouse (MDW) and the data collector in SSMS is not supported.
-
SSMS UI components that have Windows Authentication or Windows event log options do not work with Linux. You can still use these features with other options, such as SQL logins.
-
The file browser is restricted to the “C:\” scope, which resolves to /var/opt/mssql/ on Linux. To use other paths, generate scripts of the UI operation and replace the C:\ paths with Linux paths. Then execute the script manually in SSMS.
-
Number of log files to retain cannot be modified.
To begin using SQL Server on Linux, see Get started with SQL Server on Linux.
| Platform | File System | Installation Guide |
|---|---|---|
| Red Hat Enterprise Linux 7.3 Workstation, Server, and Desktop | XFS or EXT4 | Installation guide |
| SUSE Enterprise Linux Server v12 SP2 | EXT4 | Installation guide |
| Ubuntu 16.04LTS and 16.10 | EXT4 | Installation guide |
| Docker Engine 1.8+ on Windows, Mac, or Linux | N/A | Installation guide |
Note
You need at least 3.25GB of memory to run SQL Server on Linux. SQL Server Engine has been tested up to 1 TB of memory at this time.
The SQL Server engine version for this release is 14.0.304.138-1. Package details and download locations for the RPM and Debian packages are listed in the following table. Note that you do not need to download these packages directly if you use the steps in the installation guides.
| Package | Version | Downloads |
|---|---|---|
| Red Hat RPM package | 14.0.304.138-1 | mssql-server Engine RPM package mssql-server-ha High Availability RPM package mssql-server-fts Full-text Search RPM package |
| SLES RPM package | 14.0.304.138-1 | mssql-server Engine RPM package mssql-server-ha High Availability RPM package mssql-server-fts Full-text Search RPM package |
| Ubuntu 16.04 Debian package | 14.0.304.138-1 | mssql-server Engine Debian package mssql-server-ha High Availability Debian package mssql-server-fts Full-text Search Debian package |
| Ubuntu 16.10 Debian package | 14.0.304.138-1 | mssql-server Engine Debian package mssql-server-ha High Availability Debian package mssql-server-fts Full-text Search Debian package |
| Tool | Minimum version |
|---|---|
| SQL Server Management Studio (SSMS) for Windows - Release Candidate 2 | 17.0 |
| SQL Server Data Tools for Visual Studio - Release Candidate 2 | 17.0 |
| Visual Studio Code with the mssql extension | Latest (0.2.1) |
Note
The SQL Server Management Studio and SQL Server Data Tools versions specified above are Release Candidates, hence not recommended for use in production.
The following features and services are not available on Linux at this time. The support of these features will be increasingly enabled during the monthly updates cadence of the preview program.
| Area | Unsupported feature or service |
|---|---|
| Database engine | Replication |
| Stretch DB | |
| Polybase | |
| Distributed Query | |
| System extended stored procedures (XP_CMDSHELL, etc.) | |
| Filetable | |
| CLR assemblies with the EXTERNAL_ACCESS or UNSAFE permission set | |
| High Availability | |
| Database mirroring | |
| Security | Active Directory Authentication |
| Windows Authentication | |
| Extensible Key Management | |
| Use of user-provided certificate for SSL or TLS | |
| Services | SQL Server Agent |
| SQL Server Browser | |
| SQL Server R services | |
| StreamInsight | |
| Analysis Services | |
| Reporting Services | |
| Integration Services | |
| Data Quality Services | |
| Master Data Services |
The following sections describe known issues with this release of SQL Server vNext CTP 1.3 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/hostname to something 15 characters long or less.
-
Do not run the command
ALTER SERVICE MASTER KEY REGENERATE. There is a known bug that will cause SQL Server to become unstable. If you need to regenerate the Service Master Key, you should back up your database files, uninstall and then re-install SQL Server, and then restore your database files again. -
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.
-
Some time zone names in Linux don’t map exactly to Windows time zone names.
- Resolution: Use time zone names from TZID column in the ‘Mapping for: Windows’ section table on the Unicode.org documentation page.
-
SQL Server Engine expects lines in text files to be terminated with CR-LF (Windows-style line formatting).
-
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.
-
All log files and error logs are encoded in UTF-16.
-
SQL Server Configuration Manager can’t connect to SQL Server on Linux.
-
CREATE ASSEMBLY will not work when trying to use a file. Use the FROM method instead for now.
-
Changing the locations of TempDB data and log files is not supported.
-
System databases can not be moved with the mssql-conf utility.
-
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.
-
Distributed transactions requiring the Microsoft Distributed Transaction Coordinator service are not supported on SQL Server running on Linux. SQL Server to SQL Server distributed transactions are supported.
-
Always On Availability Groups in Linux may be subject to data loss if replicas are in synchronous commit mode. See Configure Always On Availability Group for SQL Server on Linux.
-
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.
-
The Korean word breaker takes several seconds to load and generates an error on first use. After this initial error, it should work normally.
- In-Memory OLTP databases can only be created in the /var/opt/mssql directory. For more information, visit the In-memory OLTP Topic.
-
Using SqlPackage requires specifying an absolute path for files. Using relative paths will map the files under the“/tmp/sqlpackage.<code>/system/system32” folder.
- Resolution: Use absolute file paths.
-
SqlPackage shows the location of files with a “C:\” prefix.
-
SQL Server Command Line tools (mssql-tools) and the ODBC Driver (msodbcsql) depends on a custom unixODBC Driver Manager. This causes conflicts if you have a previously installed unixODBC Driver Manager.
- Resolution: On Ubuntu, the conflict will be resolved automatically. When prompted if you would like to unisntall the existing unixODBC Driver Manager, type 'y' and proceed with the installation. On RedHat, you will have to remove the existing unixODBC Driver Manager manually using
yum remove unixODBC. We are working on fixing this limitation for RHEL and SUSE and should have an update for you soon.
- Resolution: On Ubuntu, the conflict will be resolved automatically. When prompted if you would like to unisntall the existing unixODBC Driver Manager, type 'y' and proceed with the installation. On RedHat, you will have to remove the existing unixODBC Driver Manager manually using
The following limitations apply to SSMS on Windows connected to SQL Server on Linux.
-
Maintenance plans are not supported.
-
Management Data Warehouse (MDW) and the data collector in SSMS is not supported.
-
SSMS UI components that have Windows Authentication or Windows event log options do not work with Linux. You can still use these features with other options, such as SQL logins.
-
The SQL Server Agent is not supported yet. Therefore, SQL Server Agent functionality in SSMS does not work on Linux at the moment.
-
The file browser is restricted to the “C:\” scope, which resolves to /var/opt/mssql/ on Linux. To use other paths, generate scripts of the UI operation and replace the C:\ paths with Linux paths. Then execute the script manually in SSMS.
-
Number of log files to retain cannot be modified.
To begin using SQL Server on Linux, see Get started with SQL Server on Linux.
| Platform | File System | Installation Guide |
|---|---|---|
| Red Hat Enterprise Linux 7.3 Workstation, Server, and Desktop | XFS or EXT4 | Installation guide |
| SUSE Enterprise Linux Server v12 SP2 | EXT4 | Installation guide |
| Ubuntu 16.04LTS and 16.10 | EXT4 | Installation guide |
| Docker Engine 1.8+ on Windows, Mac, or Linux | N/A | Installation guide |
Note
You need at least 3.25GB of memory to run SQL Server on Linux. SQL Server Engine has only been tested up to 256GB of memory at this time.
The SQL Server engine version for this release is 14.0.200.24. Package details and download locations for the RPM and Debian packages are listed in the following table. Note that you do not need to download these packages directly if you use the steps in the installation guides.
| Package | Version | Downloads |
|---|---|---|
| RPM package | 14.0.200.24-2 | mssql-server 14.0.200.24-2 Engine RPM package mssql-server 14.0.200.24-2 High Availability RPM package |
| Debian package | 14.0.200.24-2 | mssql-server 14.0.200.24-2 Engine Debian package |
| Tool | Minimum version |
|---|---|
| SQL Server Management Studio (SSMS) for Windows - Release Candidate 1 | 17.0 |
| SQL Server Data Tools for Visual Studio - Release Candidate 1 | 17.0 |
| Visual Studio Code with the mssql extension | Latest (0.2) |
Note
The SQL Server Management Studio and SQL Server Data Tools versions specified above are Release Candidates, hence not recommended for use in production.
The following features and services are not available on Linux at this time. The support of these features will be increasingly enabled during the monthly updates cadence of the preview program.
| Area | Unsupported feature or service |
|---|---|
| Database engine | Full-text Search |
| Replication | |
| Stretch DB | |
| Polybase | |
| Distributed Query | |
| System extended stored procedures (XP_CMDSHELL, etc.) | |
| Filetable | |
| CLR assemblies with the EXTERNAL_ACCESS or UNSAFE permission set | |
| High Availability | Always On Availability Groups |
| Database mirroring | |
| Security | Active Directory Authentication |
| Windows Authentication | |
| Extensible Key Management | |
| Use of user-provided certificate for SSL or TLS | |
| Services | SQL Server Agent |
| SQL Server Browser | |
| SQL Server R services | |
| StreamInsight | |
| Analysis Services | |
| Reporting Services | |
| Integration Services | |
| Data Quality Services | |
| Master Data Services |
The following sections describe known issues with this release of SQL Server vNext CTP 1.2 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/hostname to something 15 characters long or less.
-
Do not run the command
ALTER SERVICE MASTER KEY REGENERATE. There is a known bug that will cause SQL Server to become unstable. If you need to regenerate the Service Master Key, you should back up your database files, uninstall and then re-install SQL Server, and then restore your database files again. -
Resource name for SQL resource changed from ocf:sql:fci to ocf:mssql:fci. More details about configuring a shared disk failover cluster you can find here.
-
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.
-
Some time zone names in Linux don’t map exactly to Windows time zone names.
- Resolution: Use time zone names from TZID column in the ‘Mapping for: Windows’ section table on the Unicode.org documentation page.
-
SQL Server Engine expects lines in text files to be terminated with CR-LF (Windows-style line formatting).
-
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.
-
All log files and error logs are encoded in UTF-16.
-
SQL Server Configuration Manager can’t connect to SQL Server on Linux.
-
CREATE ASSEMBLY will not work when trying to use a file. Use the FROM method instead for now.
-
Changing the locations of TempDB data and log files is not supported.
-
System databases can not be moved with the mssql-conf utility.
-
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.
-
Distributed transactions requiring the Microsoft Distributed Transaction Coordinator service are not supported on SQL Server running on Linux. SQL Server to SQL Server distributed transactions are supported.
- In-Memory OLTP databases can only be created in the /var/opt/mssql directory. These databases also need to have the "C:" notation when referred. For more information, visit the In-memory OLTP Topic.
-
Using SqlPackage requires specifying an absolute path for files. Using relative paths will map the files under the“/tmp/sqlpackage.<code>/system/system32” folder.
- Resolution: Use absolute file paths.
-
SqlPackage shows the location of files with a “C:\” prefix.
-
If you have an older version of SQL Server Command Line tools (mssql-tools) and the ODBC Driver (msodbcsql), you might have installed a custom unixODBC Driver Manager (unixODBC-utf16). This could casue a potential conflict as we no longer use a custom driver manager.
- Resolution: On Ubuntu and SLES, the conflict will be resolved automatically. When prompted if you would like to unisntall the existing unixODBC Driver Manager, type 'y' and proceed with the installation. On RedHat, you will have to remove the existing unixODBC Driver Manager manually using
yum remove unixODBC-utf16 unixODBC-utf16-develand retry the install.
- Resolution: On Ubuntu and SLES, the conflict will be resolved automatically. When prompted if you would like to unisntall the existing unixODBC Driver Manager, type 'y' and proceed with the installation. On RedHat, you will have to remove the existing unixODBC Driver Manager manually using
The following limitations apply to SSMS on Windows connected to SQL Server on Linux.
-
Maintenance plans are not supported.
-
Management Data Warehouse (MDW) and the data collector in SSMS is not supported.
-
SSMS UI components that have Windows Authentication or Windows event log options do not work with Linux. You can still use these features with other options, such as SQL logins.
-
The SQL Server Agent is not supported yet. Therefore, SQL Server Agent functionality in SSMS does not work on Linux at the moment.
-
The file browser is restricted to the “C:\” scope, which resolves to /var/opt/mssql/ on Linux. To use other paths, generate scripts of the UI operation and replace the C:\ paths with Linux paths. Then execute the script manually in SSMS.
To begin using SQL Server on Linux, see Get started with SQL Server on Linux.
| Platform | File System | Installation Guide |
|---|---|---|
| Red Hat Enterprise Linux Workstation, Server, and Desktop | XFS or EXT4 | Installation guide |
| Ubuntu 16.04LTS and 16.10 | EXT4 | Installation guide |
| Docker Engine 1.8+ on Windows, Mac, or Linux | N/A | Installation guide |
Note
You need at least 3.25GB of memory to run SQL Server on Linux. SQL Server Engine has only been tested up to 256GB of memory at this time.
The SQL Server engine version for this release is 14.0.100.187. Package details and download locations for the RPM and Debian packages are listed in the following table. Note that you do not need to download these packages directly if you use the steps in the installation guides.
| Package | Version | Downloads |
|---|---|---|
| RPM package | 14.0.100.187-1 | mssql-server 14.0.100.187-1 Engine RPM package mssql-server 14.0.100.187-1 High Availability RPM package |
| Debian package | 14.0.100.187-1 | mssql-server 14.0.100.187-1 Engine Debian package |
| Tool | Minimum version |
|---|---|
| SQL Server Management Studio (SSMS) for Windows - Release Candidate 1 | 17.0 |
| SQL Server Data Tools for Visual Studio - Release Candidate 1 | 17.0 |
| Visual Studio Code with the mssql extension | Latest (0.2) |
Note
The SQL Server Management Studio and SQL Server Data Tools versions specified above are Release Candidates, hence not recommended for use in production.
The following features and services are not available on Linux at this time. The support of these features will be increasingly enabled during the monthly updates cadence of the preview program.
| Area | Unsupported feature or service |
|---|---|
| Database engine | Full-text Search |
| Replication | |
| Stretch DB | |
| Polybase | |
| Distributed Query | |
| System extended stored procedures (XP_CMDSHELL, etc.) | |
| Filetable | |
| CLR assemblies with the EXTERNAL_ACCESS or UNSAFE permission set | |
| High Availability | Always On Availability Groups |
| Database mirroring | |
| Security | Active Directory Authentication |
| Windows Authentication | |
| Extensible Key Management | |
| Use of user-provided certificate for SSL or TLS | |
| Services | SQL Server Agent |
| SQL Server Browser | |
| SQL Server R services | |
| StreamInsight | |
| Analysis Services | |
| Reporting Services | |
| Integration Services | |
| Data Quality Services | |
| Master Data Services |
The following sections describe known issues with this release of SQL Server vNext CTP 1.1 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/hostname to something 15 characters long or less.
-
Do not run the command
ALTER SERVICE MASTER KEY REGENERATE. There is a known bug that will cause SQL Server to become unstable. If you need to regenerate the Service Master Key, you should back up your database files, uninstall and then re-install SQL Server, and then restore your database files again. -
Resource name for SQL resource changed from ocf:sql:fci to ocf:mssql:fci. More details about configuring a shared disk failover cluster you can find here.
-
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.
-
Some time zone names in Linux don’t map exactly to Windows time zone names.
- Resolution: Use time zone names from TZID column in the ‘Mapping for: Windows’ section table on the Unicode.org documentation page.
-
SQL Server Engine expects lines in text files to be terminated with CR-LF (Windows-style line formatting).
-
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.
-
All log files and error logs are encoded in UTF-16.
-
SQL Server Configuration Manager can’t connect to SQL Server on Linux.
-
CREATE ASSEMBLY will not work when trying to use a file. Use the FROM method instead for now.
-
Changing the locations of TempDB data and log files is not supported.
-
System databases can not be moved with the mssql-conf utility.
-
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.
-
Distributed transactions requiring the Microsoft Distributed Transaction Coordinator service are not supported on SQL Server running on Linux. SQL Server to SQL Server distributed transactions are supported.
- In-Memory OLTP databases can only be created in the /var/opt/mssql directory. These databases also need to have the "C:" notation when referred. For more information, visit the In-memory OLTP Topic.
-
Using SqlPackage requires specifying an absolute path for files. Using relative paths will map the files under the“/tmp/sqlpackage.<code>/system/system32” folder.
- Resolution: Use absolute file paths.
-
SqlPackage shows the location of files with a “C:\” prefix.
-
SQL Server Command Line tools (mssql-tools) and the ODBC Driver (msodbcsql) depends on a custom unixODBC Driver Manager. This causes conflicts if you have a previously installed unixODBC Driver Manager.
- Resolution: On Ubuntu, the conflict will be resolved automatically. When prompted if you would like to unisntall the existing unixODBC Driver Manager, type 'y' and proceed with the installation. On RedHat, you will have to remove the existing unixODBC Driver Manager manually using
yum remove unixODBC. We are working on fixing this limitation for RHEL and SUSE and should have an update for you soon.
- Resolution: On Ubuntu, the conflict will be resolved automatically. When prompted if you would like to unisntall the existing unixODBC Driver Manager, type 'y' and proceed with the installation. On RedHat, you will have to remove the existing unixODBC Driver Manager manually using
The following limitations apply to SSMS on Windows connected to SQL Server on Linux.
-
Maintenance plans are not supported.
-
Management Data Warehouse (MDW) and the data collector in SSMS is not supported.
-
SSMS UI components that have Windows Authentication or Windows event log options do not work with Linux. You can still use these features with other options, such as SQL logins.
-
The SQL Server Agent is not supported yet. Therefore, SQL Server Agent functionality in SSMS does not work on Linux at the moment.
-
The file browser is restricted to the “C:\” scope, which resolves to /var/opt/mssql/ on Linux. To use other paths, generate scripts of the UI operation and replace the C:\ paths with Linux paths. Then execute the script manually in SSMS.
To begin using SQL Server on Linux, see Get started with SQL Server on Linux.
| Platform | File System | Installation Guide |
|---|---|---|
| Red Hat Enterprise Linux 7.2 Workstation, Server, and Desktop | XFS or EXT4 | Installation guide |
| Ubuntu 16.04LTS | EXT4 | Installation guide |
| Docker Engine 1.8+ on Windows, Mac, or Linux | N/A | Installation guide |
Note
You need at least 3.25GB of memory to run SQL Server on Linux. SQL Server Engine has only been tested up to 256GB of memory at this time.
The SQL Server engine version for this release is 14.0.1.246. Package details and download locations for the RPM and Debian packages are listed in the following table. Note that you do not need to download these packages directly if you use the steps in the installation guides.
| Package | Version | Downloads |
|---|---|---|
| RPM package | 14.0.1.246-6 | mssql-server 14.0.1.246-6 Engine RPM package mssql-server 14.0.1.246-6 High Availability RPM package |
| Debian package | 14.0.1.246-6 | mssql-server 14.0.1.246-6 Engine Debian package |
| Tool | Minimum version |
|---|---|
| SQL Server Management Studio (SSMS) for Windows - Release Candidate 1 | 17.0 |
| SQL Server Data Tools for Visual Studio - Release Candidate 1 | 17.0 |
| Visual Studio Code with the mssql extension | Latest (0.1.5) |
Note
The SQL Server Management Studio and SQL Server Data Tools versions specified above are Release Candidates, hence not recommended for use in production.
The following features and services are not available on Linux at this time. The support of these features will be increasingly enabled during the monthly updates cadence of the preview program.
| Area | Unsupported feature or service |
|---|---|
| Database engine | Full-text Search |
| Replication | |
| Stretch DB | |
| Polybase | |
| Distributed Query | |
| System extended stored procedures (XP_CMDSHELL, etc.) | |
| Filetable | |
| CLR assemblies with the EXTERNAL_ACCESS or UNSAFE permission set | |
| High Availability | Always On Availability Groups |
| Database mirroring | |
| Security | Active Directory authentication |
| Windows Authentication | |
| Extensible Key Management | |
| Use of user-provided certificate for SSL or TLS | |
| Services | SQL Server Agent |
| SQL Server Browser | |
| SQL Server R services | |
| StreamInsight | |
| Analysis Services | |
| Reporting Services | |
| Integration Services | |
| Data Quality Services | |
| Master Data Services |
The following sections describe known issues with this release of SQL Server vNext CTP1 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/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.
-
Some time zone names in Linux don’t map exactly to Windows time zone names.
- Resolution: Use time zone names from TZID column in the ‘Mapping for: Windows’ section table on the Unicode.org documentation page.
-
SQL Server Engine expects lines in text files to be terminated with CR-LF (Windows-style line formatting).
-
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.
-
All log files and error logs are encoded in UTF-16.
-
SQL Server Configuration Manager can’t connect to SQL Server on Linux.
-
CREATE ASSEMBLY will not work when trying to use a file. Use the FROM method instead for now.
-
Changing the locations of TempDB data and log files is not supported.
-
System databases can not be moved with the mssql-conf utility.
-
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.
-
Distributed transactions requiring the Microsoft Distributed Transaction Coordinator service are not supported on SQL Server running on Linux. SQL Server to SQL Server distributed transactions are supported.
- In-Memory OLTP databases can only be created in the /var/opt/mssql directory. These databases also need to have the "C:" notation when referred. For more information, visit the In-memory OLTP Topic.
-
Using SqlPackage requires to specify an absolute path for files. Using relative paths will map the files under the“/tmp/sqlpackage.<code>/system/system32” folder.
- Resolution: Use absolute file paths.
-
SqlPackage shows the location of files with a “C:\” prefix.
-
SQL Server Command Line tools (mssql-tools) and the ODBC Driver (msodbcsql) depends on a custom unixODBC Driver Manager. This causes conflicts if you have a previously installed unixODBC Driver Manager.
- Resolution: On Ubuntu, the conflict will be resolved automatically. When prompted if you would like to unisntall the existing unixODBC Driver Manager, type 'y' and proceed with the installation. On RedHat, you will have to remove the existing unixODBC Driver Manager manually using
yum remove unixODBC. We are working on fixing this limitation for RHEL and SUSE and should have an update for you soon.
- Resolution: On Ubuntu, the conflict will be resolved automatically. When prompted if you would like to unisntall the existing unixODBC Driver Manager, type 'y' and proceed with the installation. On RedHat, you will have to remove the existing unixODBC Driver Manager manually using
The following limitations apply to SSMS on Windows connected to SQL Server on Linux.
-
Maintenance plans are not supported.
-
Management Data Warehouse (MDW) and the data collector in SSMS is not supported.
-
SSMS UI components that have Windows Authentication or Windows event log options do not work with Linux. You can still use these features with other options, such as SQL logins.
-
The SQL Server Agent is not supported yet. Therefore, SQL Server Agent functionality in SSMS does not work on Linux at the moment.
-
The file browser is restricted to the “C:\” scope, which resolves to /var/opt/mssql/ on Linux. To use other paths, generate scripts of the UI operation and replace the C:\ paths with Linux paths. Then execute the script manually in SSMS.
To begin using SQL Server on Linux, see Get started with SQL Server on Linux.