Share via

ODBC Driver 13.0 for Linux Released

  • Article

Hi all, we are delighted to share the Production Ready release of the Microsoft ODBC Driver 13 for Linux –  (Ubuntu, RedHat and SUSE). The new driver enables access to SQL Server, Azure SQL Database and Azure SQL DW from any C/C++ application on Linux

What’s new

  • Native Linux Install Experience: The driver can now be installed with apt-get (Ubuntu), yum (RedHat/CentOS) and Zypper (SUSE). Instructions on how to do this is below.
  • AlwaysOn Availability Groups (AG) : The driver now supports transparent connections to AlwaysOn Availability Groups. The driver quickly discovers the current AlwaysOn topology of your server infrastructure and connects to the current active server transparently.
  • TLS 1.2 support: The driver now supports TLS 1.2 connections to SQL Server.

Install the ODBC Driver for Linux on Ubuntu 15.10

[snippet slug=odbc-rtw-15-10 lang=bsh]

Install the ODBC Driver for Linux on Ubuntu 16.04

[snippet slug=odbc-rtw-16-04 lang=bsh]

Install the ODBC Driver for Linux on RedHat 6

[snippet slug=odbc-rtw-rhel6 lang=bsh]

Install the ODBC Driver for Linux on RedHat 7

[snippet slug=odbc-rtw-rhel7 lang=bsh]

Install the ODBC Driver for SUSE12

[snippet slug=odbc-rtw-suse12 lang=bsh]

Note: Packages for SQL Server command line tools will be available soon. The above mentioned packages only install the ODBC Driver for SQL Server that enable connectivity from any C/C++ application.

Try our Sample

Once you install the driver that runs on a supported Linux distro, you can use this C sample to connect to SQL Server/Azure SQL DB/Azure SQL DW. To download the sample and get started, follow these steps:

[snippet slug=odbc-c-sample lang=bsh]

If you installed the driver using the manual instructions found here, you will have to manually uninstall the ODBC Driver and the unixODBC Driver Manager to use the deb/rpm packages. If you have any questions on how to manually uninstall, feel free to leave a comment below. 

Please fill bugs/questions/issues on our Issues page. We welcome contributions/questions/issues of any kind. Happy programming!

Survey and Future Plans

Please take this survey to help prioritize features and scenarios for the next release of the ODBC Driver for Linux. Going forward we plan to expand SQL Server 16 Feature Support (example: Always Encrypted), improve test coverage, and fix bugs reported on our Issues page.

Please stay tuned for upcoming releases that will have additional feature support and bug fixes. This applies to our wide range of client drivers including PHP 7.0, Node.js, JDBC and ADO.NET which are already available.

Meet Bhagdev (meetb@microsoft.com)

Comments

  • Anonymous
    October 19, 2016
    https://apt-mo.trafficmanager.net/yumrepos/mssql-sles12-release/ But it's mssql-suse12-release in the site, not mssql-sles12-release !We can see the directory list in the site:https://apt-mo.trafficmanager.net/yumrepos/
    • Anonymous
      October 21, 2016
      Good catch. It's updated now. Thanks Cauchy :)
  • Anonymous
    October 21, 2016
    Super Cool. Installed easily with no problems
    • Anonymous
      November 21, 2016
      Thanks :)
  • Anonymous
    October 24, 2016
    Is there any chance of a Debian driver?
    • Anonymous
      November 21, 2016
      What flavor of debian are you using?
    • Anonymous
      January 03, 2017
      Another vote for Debian (Jessie, 8.5)
  • Anonymous
    October 24, 2016
    Where can I download the source?
    • Anonymous
      November 21, 2016
      The ODBC Driver for Microsoft is not open sourced. We are looking into this right now.
      • Anonymous
        December 08, 2016
        The comment has been removed
        • Anonymous
          March 07, 2017
          Awesome thanks :) Feedback noted.
  • Anonymous
    October 26, 2016
    isql -v keeps failing after install on centos 6 (fresh install) with message IM002 Driver Manager. Data source name not found, and no default driver specified. the mssql driver itself works when testing the sample program supplied, so it seems to be unixODBC related. location of odbc.ini verified as /etc/odbc.ini and DSN configuration from working mssql version 11 installation was copied also centos 6). Tried dumbing down the parameters to bare minimum but the same error continues. seems unixODBC doesn't pick up on the correct odbc.ini file. any suggestions or help appreciated.
    • Anonymous
      November 21, 2016
      @les piech, did you follow these steps to install on CentOS 6sudo suyum-config-manager --add-repo https://apt-mo.trafficmanager.net/yumrepos/mssql-rhel6-release/yum-config-manager --enable mssql-rhel6-releasewget "http://aka.ms/msodbcrhelpublickey/dpgswdist.v1.asc"rpm --import dpgswdist.v1.ascyum remove unixODBC #to avoid conflicts during installationyum updateyum install msodbcsqlyum install unixODBC-utf16-devel #this step is optional but recommended*
  • Anonymous
    October 27, 2016
    Installed following directions: Install the ODBC Driver for Linux on Ubuntu 16.04.There is no sqlmcd executable, and I cannot find any information on this. This is not going to be useful without...
    • Anonymous
      November 21, 2016
      sqlcmd and bcp will be shipping via another package. They should be live in 1-2 months.
  • Anonymous
    October 28, 2016
    Thanks for the terrific installation instructions!Just a suggestion - you may want to mention the dependency on apt-transport-https (e.g. apt-get install apt-transport-https is required before apt-get update when installing on a Docker container for Ubuntu 16.04 https://hub.docker.com/r/library/ubuntu/).
    • Anonymous
      November 21, 2016
      Agreed :)
  • Anonymous
    October 28, 2016
    Doing this install now removes php7.0-odbc on Ubuntu 16.04, when before it would work just fine.
    • Anonymous
      October 28, 2016
      A little more detail on this. This is what happens when you try to install it with PHP ODBC already installed.root@local:/home/vagrant# apt-get install msodbcsqlReading package lists... DoneBuilding dependency treeReading state information... DoneThe following packages were automatically installed and are no longer required: gcc-5-base:i386 libltdl7:i386 libstdc++6:i386Use 'sudo apt autoremove' to remove them.The following additional packages will be installed: libodbc1-utf16 odbcinst-utf16 odbcinst1debian2-utf16 unixodbc-utf16Suggested packages: libmyodbc odbc-postgresql tdsodbcThe following packages will be REMOVED: ibm-iaccess ibm-iaccess-32bit:i386 libodbc1 libodbc1:i386 odbcinst odbcinst1debian2 odbcinst1debian2:i386 php7.0-odbcThe following NEW packages will be installed: libodbc1-utf16 msodbcsql odbcinst-utf16 odbcinst1debian2-utf16 unixodbc-utf160 upgraded, 5 newly installed, 8 to remove and 1 not upgraded.Need to get 3,762 kB of archives.After this operation, 1,125 kB disk space will be freed.Do you want to continue? [Y/n]I can't find any way to have both msodbcsql and php7.0-odbc installed at the same time, without having dependency issues.
  • Anonymous
    November 01, 2016
    The linklinegcc sample_c_linux.c -o sample_c_linux -lodbc -wlinks with the standard odbclinux libraryldd sample_c_linux linux-vdso.so.1 => (0x00007ffc65553000) libodbc.so.2 => /usr/lib/x86_64-linux-gnu/libodbc.so.2 (0x00007f97e71a8000)...If I link with the installed libmsodbcsql.so I get gcc sample_c_linux.c -o sample_c_linux -L. -lmsodbcsql -w/tmp/cciQtHac.o: In function extract_error':sample_c_linux.c:(.text+0x9e): undefined reference to SQLGetDiagRec'/tmp/cciQtHac.o: In function main':sample_c_linux.c:(.text+0x2dc): undefined reference to SQLDriverConnect'sample_c_linux.c:(.text+0x354): undefined reference to `SQLExecDirect'collect2: error: ld returned 1 exit statusSo there should be an update in the sample description in some way(I am using ubuntu 16.04)./G Hasse
  • Anonymous
    November 02, 2016
    Nice to see Linux support progressing!Any idea if/when a source distribution will be available? For example, there is no way to get the driver on Debian systems. I suppose adding the driver to the Debian package manager would solve my issue, but there are numerous other linux distros out there from others may want to connect to a SQL Server DB.
    • Anonymous
      November 21, 2016
      We are looking into this. What distro of Debian are you using?
      • Anonymous
        December 20, 2016
        Debian Jessie would definitely need to have this as well. Currently there's no clear guide on how to install it in other Linux flavours.
  • Anonymous
    November 02, 2016
    Is this suppose to install sqlcmd as well? I've installed it on CentOS 7 in a Docker image and a VM, but sqlcmd does not get installed.
    • Anonymous
      November 21, 2016
      sqlcmd and bcp will be shipping via another package. They should be live in 1-2 months.
  • Anonymous
    November 09, 2016
    The link for Linux RedHat 7 does not resolve. Can you please send me an updated link?Regards
  • Anonymous
    November 09, 2016
    This is great vs. compiling. Is there a timeline on the CLI tools that go along w/ 13.0?
    • Anonymous
      November 21, 2016
      CLI tools are on the way. You should see them by early Jan.
  • Anonymous
    November 15, 2016
    Where is bcp and sqlcmd for RedHat versions? I see the mssql-tools package available for Ubuntu and contains those commands. But I can't find this same package for any flavor of redhat.
    • Anonymous
      March 02, 2017
      The comment has been removed
  • Anonymous
    November 22, 2016
    Hello!Is connection pooling enabled for the PHP7 extension through UnixODBC?
    • Anonymous
      January 05, 2017
      Hi Daymon, yep that is correct.
  • Anonymous
    November 24, 2016
    Hello: I have follwed Install the ODBC Driver for SUSE12 instrcutions, but sqlcmd is not installed.RegardsJuan
    • Anonymous
      December 01, 2016
      sqlcmd will ship via a different package. This should be out soon :)
      • Anonymous
        December 12, 2016
        Are you sure ? As far as I can see they are available under the package mssql-tools.
        • Anonymous
          December 14, 2016
          Yes we just released them :) Give them a shot and let us know what you think of it.
    • Anonymous
      January 05, 2017
      Check the instructions now. sqlcmd should now install and work.
  • Anonymous
    November 25, 2016
    Please, compile this driver for the latest Debian distro - Debian JessieThx
  • Anonymous
    November 26, 2016
    The comment has been removed
    • Anonymous
      November 27, 2016
      I had missed the comment in the snippets that said to use ACCEPT_EULA=Y#for silent install use: ACCEPT_EULA=Y yum install msodbcsql
  • Anonymous
    November 29, 2016
    Any plans to support Ubuntu 14.04 (trusty), or provide a source release for manual install? For example, 16.04 (xenial) is not yet supported under Windows Subsystem for Linux on the stable ring.
    • Anonymous
      December 01, 2016
      Great observation! We don't have plans in the short term for this. We will add this to our backlog and wait for customer feedback.
  • Anonymous
    December 06, 2016
    It does not work for me:[unixODBC][Driver Manager]Can't open lib '/opt/microsoft/msodbcsql/lib64/libmsodbcsql-13.0.so.1.0' : file not foundbut:ls -l /opt/microsoft/msodbcsql/lib64/libmsodbcsql-13.0.so.1.0-rwxr-xr-x 1 ubuntu ubuntu 15616792 Oct 14 01:07 /opt/microsoft/msodbcsql/lib64/libmsodbcsql-13.0.so.1.0I am using an amazon ubuntu instance to do this.
    • Anonymous
      December 14, 2016
      The ODBC Driver is currently not supported on Amazon Linux. We only support Ubuntu, RedHat and SUSE
      • Anonymous
        January 02, 2017
        I am having this same issue on Ubuntu 16.04. The driver is there, but the unixODBC driver manager can't open it.
  • Anonymous
    December 08, 2016
    Not sure if this is the correct forum to report this, but I am seeing an SSL issue on Ubuntu 16.04 and RH7 when retrieving large objects from a SQL Server instance which has "Force Encryption" enabled in the instance network configuration. The same data can be retrieved if "Force Encryption" is disabled.The unixODBC log contains:[ODBC][29546][1481188157.242513][SQLGetData.c][237] Entry: Statement = 0x272c600 Column Number = 2 Target Type = -2 SQL_C_BINARY Buffer Length = 10484738 Target Value = 0xc4202e0000 StrLen Or Ind = 0xc42000c490[ODBC][29546][1481188157.438665][SQLGetData.c][501] Exit:[SQL_ERROR] Buffer = [BINARYDATA...] Strlen Or Ind = 0xc42000c490 -> 10485760 DIAG [08S01] [Microsoft][ODBC Driver 13 for SQL Server]SSL Provider: [error:80001044:lib(128):func(1):internal error:unexpected error] DIAG [08S01] [Microsoft][ODBC Driver 13 for SQL Server]Communication link failure
    • Anonymous
      December 08, 2016
      I can cause the same issue on any of our SQL instances (regardless of the "Force Encryption" setting) by setting "Encrypt=true" in the client connection string. The value of TrustServerCertificate, whether true or false, makes no difference to the behaviour.
    • Anonymous
      January 05, 2017
      Hello Ed, we are looking into this and believe we have a fix. We will keep you posted. Keep an eye out for the latest releases.
  • Anonymous
    December 09, 2016
    Hi guys, I see there is a discrepancy between the instructions on this page and on https://msdn.microsoft.com/en-us/library/hh568454(v=sql.110).aspxI prefer the way it is on this page (we're using the Red Hat 7 repo)Otherwise, great experience, but I could do without having to set an environment variable for unattended installs. We use this driver mostly in automated environments.
    • Anonymous
      January 05, 2017
      Hi Dirk, We will look into fixing the discrepancies over the next few days.
  • Anonymous
    December 09, 2016
    The comment has been removed
    • Anonymous
      January 05, 2017
      Can you try again? Seems like a transient error.
  • Anonymous
    December 13, 2016
    Hi, When you plan develop odbc-driver for debian?
  • Anonymous
    December 14, 2016
    I could really use install instructions for Debian 8.5 (jessie). My data science containers stem from Anaconda and they use Debian.
  • Anonymous
    December 20, 2016
    Can you make available packages for SLES 11? ODBC packages for SLES12 cannot be installed on SLES11.Thank you.
    • Anonymous
      June 01, 2017
      We are working on this. This should be available soon.
  • Anonymous
    December 20, 2016
    I tried installing the driver on an Ubuntu 16.04 where GDAL and PostGIS are installed, I got the following error message:Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation:The following packages have unmet dependencies: msodbcsql : Depends: unixodbc-utf16 (>= 2.3.1-1) but it is not going to be installed E: Unable to correct problems, you have held broken packages.I managed to get it installed but with the consequence that GDAL and Postgis were removed, which is not really useful.
    • Anonymous
      January 05, 2017
      We are working on this. Going forward the Microsoft ODBC Driver for Linux should work with the default unixODBC Driver managers instead of the custom ones.
  • Anonymous
    December 20, 2016
    Driver works great on a clean ubuntu 16.04 install. I have run into dependency issues with ubuntugis gdal-bin install. Looks like the conflicts are odbcinst-utf16, odbcinstdebian2-utf16, and libodbc1-utf16 are conflicting with odbcinst, odbcinstdebian2, and libodbc1...unixodbc 2.3.1-4.1? I have not tried the php7.0-odbc workaround below...any suggestions?
    • Anonymous
      January 05, 2017
      We are working on this. Going forward the Microsoft ODBC Driver for Linux should work with the default unixODBC Driver managers instead of the custom ones.
  • Anonymous
    December 20, 2016
    The comment has been removed
    • Anonymous
      January 05, 2017
      We are able to repro this bug and are looking into fixing it. You should see an update with this bug fix in one of the next sqlcmd/bcp releases (sometime this month/next month)
      • Anonymous
        January 24, 2017
        Is there a workaround for Dave's "The DSN specified an unsupported driver" error while we wait for the fix? I'm having the same issue on RHEL 7.2.Thanks,Nick
        • Anonymous
          January 25, 2017
          Yes there is. You need to install a specific version of the ODBC Driver. What version of the .rpm have you installed?
      • Anonymous
        January 27, 2017
        The comment has been removed
  • Anonymous
    December 22, 2016
    It's great job!I'd like to use ODBC Driver 13.0 for Linux in business.So when is the mainstream support end and extended support end?
    • Anonymous
      January 05, 2017
      Mainstream support is 5 years from release date. We do not have extended support for the Microsoft ODBC Driver 13 for Linux.
  • Anonymous
    December 28, 2016
    Hi,Can you give the right link to download then Install "ODBC Driver 13.0 for Linux on RedHat 7" with offline steps(no internet connectivity). we want to install odbjc 13 on Linux 7.We found below link with msi files. Is this for Windows OR Linuxservers? Please confirmhttps://www.microsoft.com/en-us/download/details.aspx?id=50420English\X64\msodbcsql.msiEnglish\X86\msodbcsql.msiWith this blog steps and required to connect internet to download to Linux server.https://blogs.msdn.microsoft.com/sqlnativeclient/2016/10/20/odbc-driver-13-0-for-linux-released/Note: We downloaded and installed on Linux 6 using below link for ODBC Driver 11 for SQL Server® - Red Hat Linux.https://www.microsoft.com/en-us/download/details.aspx?id=36437These odbc driver 11 files are "*.tar.gz ", But "ODBC driver 13" with above link are not "tar.gz". Is something missing? Please advise to download then Install "ODBC Driver 13.0 for Linux on RedHat 7" with offline steps(no internet connectivity)Thanks
    • Anonymous
      January 05, 2017
      Check out the offline instructions to install the ODBC Driver 13.0 on Linux here: https://msdn.microsoft.com/en-us/library/hh568454(v=sql.110).aspx#Anchor_0
      • Anonymous
        February 08, 2017
        For offline installation for Redhat 7.xIs there any plane to release "ODBC Driver 13.0 for Linux" like “*.tar.gz “ files. Similar like ODBC 11 "https://www.microsoft.com/en-us/download/details.aspx?id=36437" ?thanks
  • Anonymous
    January 05, 2017
    I would like to add a feature request to remove the dependency on unixodbc utf16.
  • Anonymous
    January 11, 2017
    Hi there,I'm probably doing something incredibly stupid (as I'm not massively experienced with Ubuntu/Linux ) but even though I follow all steps correctly and without receiving errors, I still receive a "command not found" when I try to use either bcp or sqlcmd. are there any OTHER prior or subsequent steps or commands that are not listed here that I need to perform in order to use them?
    • Anonymous
      January 13, 2017
      Hi Dylan, this is because the latest release requires you to create symlinks. Symlink: ln -sfn /opt/mssql-tools/bin/sqlcmd-13.0.1.0 /usr/bin/sqlcmd ln -sfn /opt/mssql-tools/bin/bcp-13.0.1.0 /usr/bin/bcp
  • Anonymous
    January 13, 2017
    What is the status of fixing the following issue:Dependency Resolution Error:unixODBC-utf16 conflicts with unixODBC-2.3.1-11.x86_64When will the SQL tools package be updated to allow it to use unixODBC-2.3.1-11.x86_64 instead of unixODBC-utf16? unixODBC-2.3.1-11.x86_64 is the standard install on RHEL 7. We cannot uninstall it due to other prereqs it has.Thanks
    • Anonymous
      January 13, 2017
      Our next release (in 2 weeks) should have a fix for this. Stay tuned!
      • Anonymous
        January 23, 2017
        Do we have exact date for releasing? I still face the issue
      • Anonymous
        February 17, 2017
        is this already resolved? im installing ODBC for RHEL 6 and still am getting this error:Error: unixODBC-utf16 conflicts with unixODBC-2.3.1-4.el6.x86_64Error: msodbcsql conflicts with unixODBC-utf16-2.3.1-1.x86_64
  • Anonymous
    January 17, 2017
    Hi. I'm getting segmentation fault on Ubuntu 16.04 when running bcp against an Azure SQL database.I've installed SQL Server Tools on Linux as described here: https://docs.microsoft.com/en-us/sql/linux/sql-server-linux-setup-tools#ubuntuSegmentation fault examples:bcp mytable out myfile.csv -c -t ';' -U myuser -P mypass -S myserver.database.secure.windows.net -d mydatabaseSegmentation fault (core dumped)orbcp mytable out myfile.csv -U myuser -P mypass -S myserver.database.secure.windows.net -d mydatabaseSegmentation fault (core dumped)Versionbcp -vBCP - Bulk Copy Program for Microsoft SQL Server.Copyright (C) Microsoft Corporation. All Rights Reserved.Version: 13.0.0001.0Running bcp via gdb(gdb) runProgram received signal SIGSEGV, Segmentation fault.gdb backtrace(gdb) bt#0 do_lookup_x (undef_name=undef_name@entry=0x7ffff646c773 "SQLSetConnectAttr", new_hash=new_hash@entry=2786641222, old_hash=old_hash@entry=0x7fffffff8760, ref=0x0, result=result@entry=0x7fffffff8770, scope=, i=0, version=0x0, flags=2, skip=0x0, type_class=0, undef_map=0x7ffff7ff7540) at dl-lookup.c:366#1 0x00007ffff7de194f in _dl_lookup_symbol_x (undef_name=0x7ffff646c773 "SQLSetConnectAttr", undef_map=0x7ffff7ff7540, ref=0x7fffffff8848, symbol_scope=0x7ffff7ff78c8, version=0x0, type_class=0, flags=2, skip_map=0x0) at dl-lookup.c:829#2 0x00007ffff6d28cc3 in do_sym (handle=0x7ffff7ff7540, name=0x7ffff646c773 "SQLSetConnectAttr", who=, vers=vers@entry=0x0, flags=flags@entry=2) at dl-sym.c:168#3 0x00007ffff6d2916d in _dl_sym (handle=, name=, who=) at dl-sym.c:273#4 0x00007ffff7bd4034 in dlsym_doit (a=a@entry=0x7fffffff8a50) at dlsym.c:50#5 0x00007ffff7de7394 in _dl_catch_error (objname=0x6424a0, errstring=0x6424a8, mallocedp=0x642498, operate=0x7ffff7bd4020 , args=0x7fffffff8a50) at dl-error.c:187#6 0x00007ffff7bd4571 in _dlerror_run (operate=operate@entry=0x7ffff7bd4020 , args=args@entry=0x7fffffff8a50) at dlerror.c:163#7 0x00007ffff7bd4088 in __dlsym (handle=, name=name@entry=0x7ffff646c773 "SQLSetConnectAttr") at dlsym.c:70#8 0x00007ffff63d3963 in LoadODBC32AndGetFunctions () at Sql/Ntdbms/sqlncli/odbcbcp/bcpstub.cpp:1130#9 0x00007ffff63d442d in LoadODBC32AndGetFunctions () at Sql/Ntdbms/sqlncli/odbcbcp/bcpstub.cpp:555#10 ExportImp::bcp_initW (hdbc=0x646a90, table=0x7fffffff8ae0 L"...", , file=0x7fffffff8df0 L"...", , errfile=0x0, direction=2)at Sql/Ntdbms/sqlncli/odbcbcp/bcpstub.cpp:537#11 0x00007ffff63d4515 in bcp_initA (hdbc=0x646a90, table=0x7fffffff8ae0 "s", file=0x7fffffff8df0 "/", errfile=0x0, direction=2) at Sql/Ntdbms/sqlncli/odbcbcp/bcpstub.cpp:512#12 0x000000000040546c in main (argc=, argv=) at Sql/Ntdbms/sqlncli/utils/bcp/src/bulkmain.c:650nm -C /opt/microsoft/msodbcsql/lib64/libmsodbcsql-13.1.so.1.0 | grep SQLSetConnectAttr00000000003eafe8 b pfnSQLSetConnectAttr00000000000e5220 T SQLSetConnectAttr00000000000e53c0 T SQLSetConnectAttrW00000000000e28d0 t ExportImp::SQLSetConnectAttrW(tagDBC*, int, unsigned long, int)0000000000187910 r ExportImp::SQLSetConnectAttrW(tagDBC*, int, unsigned long, int)::__func__Has anyone else experienced segmentation fault running bcp on Linux? Could it be ODBC related? (see LoadODBC32AndGetFunctions and SQLSetConnectAttr in the gdb backtrace above)Thanks
    • Anonymous
      March 02, 2017
      Hi Chirstian, we are looking into this. Can you also file a connect issue for this? https://connect.microsoft.com/
    • Anonymous
      March 06, 2017
      Hi, I created a connect issue for this: https://connect.microsoft.com/SQLServer/feedback/details/3126904We are investigating this issue. Can you help answer the following quesitons? 1.) What platform are you using?2.) What dirver manager are you using by running the command => odbcinst –j?3.) Run a ‘ldd’ to get the dependencies of the driver and the bcp binaries? (ldd which bcp, ls -l which bcp, ldd /opt/microsoft/msodbcsql/lib64/libmsodbcsql-13.0.so.1.0)Thanks,Meet
  • Anonymous
    January 23, 2017
    The comment has been removed
    • Anonymous
      January 24, 2017
      The comment has been removed
  • Anonymous
    February 06, 2017
    Version '13.0.1.0-1' for 'msodbcsql' was not found
    • Anonymous
      March 02, 2017
      Should be fixed now :) Can you try again?
  • Anonymous
    February 07, 2017
    I'm getting this error on both ubuntu 16.04 and centos 6.8:i remove all installed odbc packages and still get error. # apt install mssql-toolsPreparing to unpack .../msodbcsql_13.1.4.0-1_amd64.deb ...Installation failed, ODBC Driver 13 for SQL Server detected!dpkg: error processing archive /var/cache/apt/archives/msodbcsql_13.1.4.0-1_amd64.deb (--unpack): subprocess new pre-installation script returned error exit status 1
    • Anonymous
      February 08, 2017
      Hi Kurt, Can you share your installation steps with us?
    • Anonymous
      February 23, 2017
      The comment has been removed
  • Anonymous
    February 08, 2017
    Hi,after command 'apt-get update', when i try to install msodbcsql=13.0.1.0-1 and mssql-tools, apt reply "Can not find the package msodbcsql mssql-tools".Any suggestions?Thanks.Server Ubuntu 16.04.1 LTS and PHP7.0
    • Anonymous
      March 02, 2017
      This should now be fixed :)
  • Anonymous
    February 12, 2017
    The comment has been removed
  • Anonymous
    February 15, 2017
    I'm facing a trouble with this driver, select sql statement returns always null if nvarchar column has more than 16 multibyte characters.I have reported it on the issues page. https://connect.microsoft.com/SQLServer/feedback/details/3122522Is there any way to work around this?
    • Anonymous
      February 16, 2017
      appending:It seems that this behavior happens if the characters length more than one third of the column definition length.One third of 50 is 16.6666...If nvarchar(15) columns has more than 5 length multibyte characters, this behavior is reproduced.
    • Anonymous
      March 02, 2017
      I replied on the connect issue :) Do you have a repro script?
  • Anonymous
    February 16, 2017
    I followed steps to install ODBC on Centos 7 (RH7) and when we try to test the connection we keep getting below error.[ ~]$ isql -v TEST [28000][unixODBC][Microsoft][ODBC Driver 13 for SQL Server][SQL Server]Login failed for user ''.[ISQL]ERROR: Could not SQLConnect
    • Anonymous
      June 01, 2017
      Seems like the password/username was not correct. Are you using sql login or integrated auth?
  • Anonymous
    March 01, 2017
    The comment has been removed
    • Anonymous
      March 01, 2017
      This on Red hat 7.3 server
    • Anonymous
      March 02, 2017
      Seems like a BCP bug. Can you file a connect issue with your legs and repro steps: https://connect.microsoft.com/ and send an email to meetb@microsoft.com
      • Anonymous
        April 07, 2017
        This issue fixed with new RPM of "03-Feb-2017" release.thanks
        • Anonymous
          April 10, 2017
          Thanks for verifying :)
  • Anonymous
    March 28, 2017
    The comment has been removed
  • Anonymous
    April 05, 2017
    Is this driver available for ppc64 architecture? (SLES for SAP Applications 11.4 (ppc64) - Kernel 3.0.101-80-default)
    • Anonymous
      April 10, 2017
      Hi Alberto, we do not support ppc64 architecture. We would love to learn more about your scenarios. Can you create a new feedback item for this here: https://connect.microsoft.com/SQLServer/
  • Anonymous
    April 24, 2017
    Can this work on Cloudlinux version 6.9. Should I just use the Centos 6 instructions?
    • Anonymous
      June 01, 2017
      Cloudlinux version 6.9 is unfortunately not supported. We currently support CentOS 6,7 Ubuntu 15.x, 16.x, RHEL 6, 7 and SLES 12.
  • Anonymous
    May 23, 2017
    Is there any way to skip unixODBC installation again if it is already installaed on the server? I have already installed unixODBC and using this for DB2 database connectivity. I don't wnat to re-install and configure it?
  • Anonymous
    May 24, 2017
    I'm following the instructions to install on Ubuntu 16.04, and when I get to the step to actually install the packages, I get "Unable to locate package msodbcsql" and "Unable to locate package mssql-tools". I'm running Ubuntu 16.04.2 if that matters. Thank you!
    • Anonymous
      May 24, 2017
      Ah, I think I may know what might be happening. I just updated this machine from Ubuntu 14.04 32-bit to 16.04 32-bit. Maybe the packages are only for 64 bit, so it can't find appropriate packages that match the architecture? Think that is the case?
      • Anonymous
        June 01, 2017
        That is correct. Packages only work for a 64-bit architecture.