Odbc Disable Microsoft Transaction Server' title='Odbc Disable Microsoft Transaction Server' />Release notes for SQL Server 2. Linux. The following release notes apply to SQL Server 2. Linux. The topic below is broken into sections for each release. The GA release has detailed supportability and known issues listed. FIX Setting of connection attribute fails when you use connection pooling for the SQL Server ODBC connection. Odbc Disable Microsoft Transaction Server' title='Odbc Disable Microsoft Transaction Server' />Each Cumulative Update CU release has a link to a support topic describing the CU changes as well as links to the Linux package downloads. Supported platforms. Release history. The following table lists the release history for SQL Server 2. Release. Version. Release date. CU1. GA1. 4. 0. 1. 00. Watch videos and look at available classes to better help you get trained to understand the best ways to run the Server Application Monitor SAM. Cumulative Update 1 October 2. This is the Cumulative Update 1 CU1 release of SQL Server 2. The SQL Server engine version for this release is 1. Sonar X2 Serial Number Cracker. For information about the fixes and improvements in this release, see https support. Installation. If you have configured the Cumulative Update repository, then you will get the latest cumulative update of SQL Server packages when you perform new installations. The Cumulative Update repository is the default for all package installation articles for SQL Server on Linux. For more information about repository configuration, see Source repositories. If you are updating existing SQL Server packages, run the appropriate update command for each package to get the latest cumulative update. For specific update instructions for each package, see the following installation guides Package details. For manual or offline package installations, you can download the RPM and Debian packages with the information in the following table GA October 2. This is the General Availability GA release of SQL Server 2. The SQL Server engine version for this release is 1. Package details. 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 following installation guides Unsupported features and services. The following features and services are not available on Linux at this time. The support of these features will be increasingly enabled over time. Area. Unsupported feature or service. Database engine. Transactional replication Merge replication Stretch DB Polybase Distributed query with 3rd party connections System extended stored procedures XPCMDSHELL, etc. Filetable, FILESTREAM CLR assemblies with the EXTERNALACCESS or UNSAFE permission set Buffer Pool Extension. SQL Server Agent. Subsystems Cmd. Exec, Power. Shell, Queue Reader, SSIS, SSAS, SSRS Alerts Log Reader Agent Change Data Capture Managed Backup. High Availability. Database mirroring. Security. Extensible Key Management AD Authentication for Linked Servers AD Authentication for Availability Groups AGs 3rd party AD tools Centrify, Vintela, PowerbrokerServices. SQL Server Browser SQL Server R services Stream. Insight Analysis Services Reporting Services Data Quality Services Master Data Services. Known issues. The following sections describe known issues with the Genera Availability GA release of SQL Server 2. Linux. General. Upgrades to the GA release of SQL Server 2. CTP 2. 1 or higher. The length of the hostname where SQL Server is installed needs to be 1. Resolution Change the name in etchostname to something 1. 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 cant 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 cannot 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. 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. 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. SQL Server on Linux to disable problematic cipher suites, by doing the following Add the following to varoptmssqlmssql. AES2. 56 GCM SHA3. AES1. 28 GCM SHA2. AES2. 56 SHA2. 56 AES1. SHA2. 56 AES2. 56 SHA AES1. SHA ECDHE RSA AES1. GCM SHA2. 56 ECDHE RSA AES2. GCM SHA3. 84 ECDHE ECDSA AES2. GCM SHA3. 84 ECDHE ECDSA AES1. GCM SHA2. 56 ECDHE ECDSA AES2. SHA3. 84 ECDHE ECDSA AES1. SHA2. 56 ECDHE ECDSA AES2. SHA ECDHE ECDSA AES1. SHA ECDHE RSA AES2. SHA3. 84 ECDHE RSA AES1. SHA2. 56 ECDHE RSA AES2. SHA ECDHE RSA AES1. SHA DHE RSA AES2. GCM SHA3. 84 DHE RSA AES1. GCM SHA2. 56 DHE RSA AES2. SHA DHE RSA AES1. SHA DHE DSS AES2. SHA2. 56 DHE DSS AES1. SHA2. 56 DHE DSS AES2. SHA DHE DSS AES1. SHA DHE DSS DES CBC3 SHA NULL SHA2. NULL SHA. Note. In the preceding code, This tells Open. SSL to not use the following cipher suite. Restart SQL Server with the following command. SQL Server 2. 01. Windows that use In memory OLTP cannot be restored on SQL Server 2. Linux. To restore a SQL Server 2. OLTP, first upgrade the databases to SQL Server 2. SQL Server 2. 01. Windows before moving them to SQL Server on Linux via backuprestore or detachattach. 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 The target server is specified as a hostname and not an IP address. The source instance has IPv. To verify if your system has IPv. The output must not contain ipv. The procsysnetipv. A C program that calls socketAFINET6, SOCKSTREAM, IPPROTOIP 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 Use IPs instead of hostnames to specify the target of the TCP connection. Enable IPv. 6 in the kernel by removing ipv. The way to do this depends on the Linux distribution and the bootloader, such as grub. If you do want IPv. This will still prevent the systems network adapter from getting an IPv. Network File System NFSIf you use Network File System NFS remote shares in production, note the following support requirements Use NFS version 4. Older versions of NFS do not support required features, such as fallocate and sparse file creation, common to modern file systems. Locate only the varoptmssql 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. PHP odbcconnect Manual. Two additional notes regarding ODBC connections to a Network Sybase SQL Anywhere 8 Server. I wrote a script using the PHP5 CLI binary that monitors a directory for changes, then updates a Network Server SQL Anywhere 8 database when a change was detected. Idealy, my program would run indefinately, and issue odbcconnectodbcclose when appropriate. However, it seems that once connected, your odbc session is limited to 3. Instead, it returns a generic Authentication violation  error from the odbc driver. Heres an example lt Additionally, it seems that odbcclose doesnt truely close the connection at least not using Network SQL Anywhere 8. The resource is no longer usable after the odbcclose is issued, but as far as the server is concerned, there is still a connection present. The connection doesnt truely close until after the php script has ended, which is unfortunate, because a subsequent odbcconnect commands appear to reuse the existing stale connection, which was supposedly closed. My workaround was to design my script exit entirely after a the database update had completed. I then called my script whithin a batch file and put it inside an endless loop. Im not sure if this is a bug with PHP or what, but I thought Id share in case someone else is pulling their hair out trying to figure this one out.