Using python (pyodbc) I tested the throughput of the SQL Server, ODBC Driver 13 for SQL Server, and SQL Server Native Client 11.0 drivers. The SQL Server driver was consistently over 10% slower than the other two options for select statements and around 50% slower for insert statements. In this article, we will explain how to install the appropriate ODBC drivers for SQL Server, how to configure ODBC to connect to a SQL Server instance and how to create and configure a Linked Server using the ODBC driver and the MSDASQL provider to query tables on a SQL Server instance.

1. Sql Server Odbc Driver 10 5
2. Sql Server Odbc Driver 10 Codes
3. Sql Server Odbc Driver 10 Download
4. Sql Server Native Client 10 Odbc Driver Download

• Aug 09, 2017  Download ODBC Driver. ODBC is the primary native data access API for applications written in C and C for SQL Server. There is an ODBC driver for most data sources. Other languages that can use ODBC include COBOL, Perl, PHP, and Python. ODBC is widely used in data integration scenarios. The ODBC driver comes with tools such as sqlcmd and bcp.
• Installing the Microsoft ODBC Driver for SQL Server on Linux and macOS.; 12 minutes to read +4; In this article. Download ODBC Driver. This article explains how to install the Microsoft ODBC Driver for SQL Server on Linux and macOS, as well as the optional Command-Line Tools for SQL Server (bcp and sqlcmd) and the unixODBC Development Headers.
• Using python (pyodbc) I tested the throughput of the SQL Server, ODBC Driver 13 for SQL Server, and SQL Server Native Client 11.0 drivers. The SQL Server driver was consistently over 10% slower than the other two options for select statements and around 50% slower for insert statements.
• The Microsoft ODBC Driver for SQL Server allows native C and C applications to leverage the standard ODBC API and connect to Microsoft SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016 (Preview), Analytics Platform System, Azure SQL Database and Azure SQL Data Warehouse.

-->

This article explains how to install the Microsoft ODBC Driver for SQL Server on Linux and macOS, as well as the optional Command-Line Tools for SQL Server (bcp and sqlcmd) and the unixODBC Development Headers.

Microsoft ODBC Driver 17 for SQL Server

Important

The program supports more compression formats than the default tool in Mac OS. DownloadBy default, in Mac OS a tool integrated for the extraction of zip files and other compression formats. There are also free alternatives to this tool that has more functionality to offer. In addition, The Unarchiver is a nice design, and supports foreign characters (such as those from the Japanese language).supports the extraction of the following file formats:has the following characteristics:The Unarchiver screenshotsYou can free download The Unarchiver and safe install the latest trial or new full version for Windows 10 (x32, 64 bit, 86) from the official site.Devices: Desktop PC, Laptop (ASUS, HP, DELL, Acer, Lenovo, MSI), UltrabookOS: Professional, Enterprise, Education, Home Edition, versions: 1507, 1511, 1607, 1703, 1709, 1803, 1809 Categories. The Unarchiver is an example of this.The Unarchiver is a free program for Mac to archive files to extract. Unarchiver for windows 10.

If you installed the v17 msodbcsql package that was briefly available, you should remove it before installing the msodbcsql17 package. This will avoid conflicts. The msodbcsql17 package can be installed side by side with the msodbcsql v13 package.

Debian

RedHat Enterprise Server

SUSE Linux Enterprise Server

Ubuntu

Note

• Driver version 17.2 or higher is required for Ubuntu 18.04 support.
• Driver version 17.3 or higher is required for Ubuntu 18.10 support.

MacOS

Microsoft ODBC Driver 13.1 for SQL Server

Debian 8

RedHat Enterprise Server 6

RedHat Enterprise Server 7

SUSE Linux Enterprise Server 11

SUSE Linux Enterprise Server 12

Ubuntu 15.10

Ubuntu 16.04

Ubuntu 16.10

OS X 10.11 (El Capitan) and macOS 10.12 (Sierra)

Microsoft ODBC Driver 13 for SQL Server

RedHat Enterprise Server 6

RedHat Enterprise Server 7

Ubuntu 15.10

Ubuntu 16.04

SUSE Linux Enterprise Server 12

Offline installation

If you prefer/require the Microsoft ODBC Driver 13 to be installed on a computer with no internet connection, you will need to resolve package dependencies manually. The Microsoft ODBC Driver 13 has the following direct dependencies:

• Ubuntu: libc6 (>= 2.21), libstdc++6 (>= 4.9), libkrb5-3, libcurl3, openssl, debconf (>= 0.5), unixodbc (>= 2.3.1-1)
• Red Hat: glibc, e2fsprogs, krb5-libs, openssl, unixODBC
• SuSE: glibc, libuuid1, krb5, openssl, unixODBC

Each of these packages in turn has their own dependencies, which may or may not be present on the system. For a general solution to this issue, refer to your distribution's package manager documentation: Redhat, Ubuntu, and SUSE

It is also common to manually download all the dependent packages and place them together on the installation computer, then manually install each package in turn, finishing with the Microsoft ODBC Driver 13 package.

Redhat Linux Enterprise Server 7

• Download the latest msodbcsql.rpm from here: https://packages.microsoft.com/rhel/7/prod/
• Install dependencies and the driver

Ubuntu 16.04

• Download the latest msodbcsql.deb from here: https://packages.microsoft.com/ubuntu/16.04/prod/pool/main/m/msodbcsql/
• Install dependencies and the driver

SUSE Linux Enterprise Server 12

• Download the latest msodbcsql.rpm from here: https://packages.microsoft.com/sles/12/prod/
• Install the dependencies and the driver

Once you have completed the package installation, you can verify that the Microsoft ODBC Driver 13 can find all its dependencies by running ldd and inspecting its output for missing libraries:

Microsoft ODBC Driver 11 for SQL Server on Linux

Before you can use the driver, install the unixODBC driver manager. For more information, see Installing the Driver Manager.

Installation Steps

Important

These instructions refer to msodbcsql-11.0.2270.0.tar.gz, which is installation file for Red Hat Linux. If you are installing the Preview for SUSE Linux, the file name is msodbcsql-11.0.2260.0.tar.gz.

To install the driver:

1. Make sure that you have root permission.

2. Change to the directory where the download placed the file msodbcsql-11.0.2270.0.tar.gz. Make sure that you have the *.tar.gz file that matches your version of Linux. To extract the files, execute the following command, tar xvzf msodbcsql-11.0.2270.0.tar.gz.

3. Change to the msodbcsql-11.0.2270.0 directory and there you should see a file called install.sh.

4. To see a list of the available installation options, execute the following command: ./install.sh.

5. Make a backup of odbcinst.ini. The driver installation updates odbcinst.ini. odbcinst.ini contains the list of drivers that are registered with the unixODBC Driver Manager. To discover the location of odbcinst.ini on your computer, execute the following command: odbc_config --odbcinstini.

6. Before you install the driver, execute the following command: ./install.sh verify. The output of ./install.sh verify reports if your computer has the required software to support the ODBC driver on Linux.

7. When you are ready to install the ODBC driver on Linux, execute the command: ./install.sh install. If you need to specify an install command (bin-dir or lib-dir), specify the command after the install option.

8. After reviewing the license agreement, type YES to continue with the installation.

Installation puts the driver in /opt/microsoft/msodbcsql/11.0.2270.0. The driver and its support files must be in /opt/microsoft/msodbcsql/11.0.2270.0.

To verify that the Microsoft ODBC driver on Linux was registered successfully, execute the following command: odbcinst -q -d -n 'ODBC Driver 11 for SQL Server'.

Use Existing MSDN C++ ODBC Samples for the ODBC Driver on Linux shows a code sample that connects to SQL Server using the ODBC driver on Linux. Green screen christmas backgrounds.

Uninstalling

You can uninstall the ODBC driver 11 on Linux by executing the following commands:

1. rm -f /usr/bin/sqlcmd

2. rm -f /usr/bin/bcp

3. rm -rf /opt/microsoft/msodbcsql

4. odbcinst -u -d -n 'ODBC Driver 11 for SQL Server'

Troubleshooting Connection Problems

If you are unable to make a connection to SQL Server using the ODBC driver, use the following information to identify the problem.

The most common connection problem is to have two copies of the UnixODBC Driver Manager installed. Search /usr for libodbc*.so*. If you see more than one version of the file, you (possibly) have more than one driver manager installed. Your application might use the wrong version.

Enable the connection log by editing your /etc/odbcinst.ini file to contain the following section with these items:

If you get another connection failure and do not see a log file, there (possibly) are two copies of the driver manager on your computer. Otherwise, the log output should be similar to the following:

If the ASCII character encoding is not UTF-8, for example:

There is more than one Driver Manager installed and your application is using the wrong one, or the Driver Manager was not built correctly.

For more information about resolving connection failures, see:

• The error number specified in the URL (11001) should be changed to match the error that you see.

Driver Files

The ODBC Driver on Linux and MacOS consists of the following components:

Linux

Component	Description
libmsodbcsql-17.X.so.X.X or libmsodbcsql-13.X.so.X.X	The shared object (so) dynamic library file that contains all of the driver's functionality. This file is installed in /opt/microsoft/msodbcsql17/lib64/ for the Driver 17 and in /opt/microsoft/msodbcsql/lib64/ for Driver 13.
msodbcsqlr17.rll or msodbcsqlr13.rll	The accompanying resource file for the driver library. This file is installed in [driver .so directory]./share/resources/en_US/
msodbcsql.h	The header file that contains all of the new definitions needed to use the driver. Note: You cannot reference msodbcsql.h and odbcss.h in the same program. msodbcsql.h is installed in /opt/microsoft/msodbcsql17/include/ for Driver 17 and in /opt/microsoft/msodbcsql/include/ for Driver 13.
LICENSE.txt	The text file that contains the terms of the End-User License Agreement. This file is placed in /usr/share/doc/msodbcsql17/ for Driver 17 and in /usr/share/doc/msodbcsql/ for Driver 13.
RELEASE_NOTES	The text file that contains release notes. This file is placed in /usr/share/doc/msodbcsql17/ for Driver 17 and in /usr/share/doc/msodbcsql/ for Driver 13.

MacOS

Component	Description
libmsodbcsql.17.dylib or libmsodbcsql.13.dylib	The dynamic library (dylib) file that contains all of the driver's functionality. This file is installed in /usr/local/lib/.
msodbcsqlr17.rll or msodbcsqlr13.rll	The accompanying resource file for the driver library. This file is installed in [driver .dylib directory]./share/msodbcsql17/resources/en_US/ for Driver 17 and in [driver .dylib directory]./share/msodbcsql/resources/en_US/ for Driver 13.
msodbcsql.h	The header file that contains all of the new definitions needed to use the driver. Note: You cannot reference msodbcsql.h and odbcss.h in the same program. msodbcsql.h is installed in /usr/local/include/msodbcsql17/ for Driver 17 and in /usr/local/include/msodbcsql/ for Driver 13.
LICENSE.txt	The text file that contains the terms of the End-User License Agreement. This file is placed in /usr/local/share/doc/msodbcsql17/ for Driver 17 and in /usr/local/share/doc/msodbcsql/ for Driver 13.
RELEASE_NOTES	The text file that contains release notes. This file is placed in /usr/local/share/doc/msodbcsql17/ for Driver 17 and in /usr/local/share/doc/msodbcsql/ for Driver 13.

Resource File Loading

The driver needs to load the resource file in order to function. This file is called msodbcsqlr17.rll or msodbcsqlr13.rll depending on the driver version. The location of the .rll file is relative to the location of the driver itself (so or dylib), as noted in the table above. As of version 17.1 the driver will also attempt to load the .rll from the default directory if loading from the relative path fails. The default resource file paths are:

Linux: /opt/microsoft/msodbcsql17/share/resources/en_US/

MacOS: /usr/local/share/msodbcsql17/resources/en_US/

See Also

I was setting up the System DSN (64 bit) for my database in SQL server 2016 with Windows 10 64 bit pro. While I was asked to choose the driver to set up a data source, there are the following selections:

• ODBC Driver 13 for SQL Server
• SQL Server
• SQL Server Native Client 11.0
• SQL Server Native Client RDA 11.0

It seemed I can set up the data source with all of these drivers. Then which one should I choose in terms of speed and efficiency? What's the difference between them?

Thanks,

Jason

JasonJason

4 Answers

ODBC Driver for SQL Server

ODBC is the primary native data access API for applications written in C,C++, PHP, Python and others for connecting to SQL Server.

It's widely used in data integration scenarios.

Also, it's preferred if you are developing application on Windows and deploying it to Linux .

SQL Server

The full name of SQL Server Driver is SQL Server ODBC Driver. It’s an old driver since sql 2000. You can use it to connect to SQL Server 2016, but you will not be able to access new features and functionality of SQL Server 2016

SQL Server Native Client

SQL Server Native Client is containing both the SQL OLE DB provider and SQL ODBC driver to support native connectivity to SQL Server and support all features of sql server 2016. It's the best in windows environment

SQL Server Native Client RDA

Remote data access (RDA) in Microsoft SQL Server Compact 3.5 lets an application access data from a remote SQL Server database table.

It can also store, read, and update that data in SQL Server Compact 3.5, and then update the original SQL Server table.

RDA will be removed in the future release, so avoid using it.

So choose sql driver based on the criteria above.

M.HassanM.Hassan

Microsoft ODBC Driver for SQL Server (MSODBCSQL)

This driver was announced in 2013 as the successor to SQL Server Native Client. It is installed with recent SQL Server versions (13 with 2016 and 2017). There are also standalone installers. Driver history for Microsoft SQL Server recommends this driver in preference to 'SQL Server' and 'SQL Server Native Client' for ODBC. Added features over 'SQL Server Native Client': driver-aware connection pooling, connection resiliency, and asynchronous execution (polling). You can follow current development on the Microsoft ODBC Driver For SQL Server Team blog.

Driver={ODBC Driver XX for SQL Server} (XX for installed version. See System Requirements, Installation, and Driver Files.)

SQL Server Native Client (SQLNCLI)

Introduced with SQL Server 2005 and ships with SQL Server (also installable via sqlncli.msi from SQL Server feature packs). Added features over 'SQL Server': Multiple active result sets (MARS), user-defined data types (UDT), query notifications, snapshot isolation, and XML data type support.

Driver={SQL Server Native Client} (SQL Server 2005)
Driver={SQL Server Native Client 10.0} (SQL Server 2008)
Driver={SQL Server Native Client 11.0} (SQL Server 2012 and later)

SQL Server Native Client RDA

Remote Data Access (RDA) is a SQL Server Compact feature which 'lets an application access data from a remote SQL Server database table.' I can't find much documentation, but it appears this driver was intended to support replication scenarios with Compact Edition.

SQL Server (SQLSRV32)

Included in Microsoft Data Access Components (MDAC) (now called Windows Data Access Components (WDAC)). This driver is available by default on Windows (since 98 and NT 4.0).

Driver={SQL Server}

SQL Server Native client vs .NET Framework Data Provider for ODBC

It seems that for last version for SQL Server Native client, the Microsoft® SQL Server® 2012 Native Client also named as SQL Server native client 11.0.Doesn’t support new feature in SQL Server 2014 or later

Note that SNAC 11 does not support features released with SQL Server 2014 and SQL Server 2016 that were not available as part of SQL Server 2012, such as Transparent Network IP Resolution, Always Encrypted, Azure AD Authentication, Bulk Copy and Table Value Parameters.

You have to use Microsoft® ODBC Driver 11 or 13 for SQL Server to enjoy new feature in SQL Server 2014 or later

To check which drivers you have installed, fire up an powershell (32/64 bit - depending which driver architecture you want to use) and run

OLEDB

ODBC

There are three distinct generations of Microsoft ODBC drivers for SQL Server.

• The first 'SQL Server' ODBC driver still ships as part of Windows Data Access Components. It is not recommended to use this driver for new development.
• Starting in SQL Server 2005, the SQL 'Server Native Client 10.x/11.x/12.x' includes an ODBC interface and is the ODBC driver that shipped with SQL Server 2005 through SQL Server 2012. It is not recommended to use this driver for new development.
• After SQL Server 2012, the Microsoft ODBC Driver for SQL Server is the driver that is updated with the most recent server features going forward.

SQL Server

It's the old one from the MDAC-package (https://support.microsoft.com/en-us/help/899456) which now (since XP/2003) comes with the Windows-OS.https://docs.microsoft.com/en-us/sql/connect/connect-history#mdacwdac-releases

Sql Server Odbc Driver 10 5

..starting with Windows Vista, the data access components are now called Windows Data Access Components, or Windows DAC). Although both provide native data access to SQL Server databases, SQL Server Native Client has been specifically designed to expose the new features of SQL Server 2005 (9.x), while at the same time maintaining backward compatibility with earlier versions.

SQL Server Native Client

SQL Server Native Client is a stand-alone library that is used for both OLE DB and ODBC. SQL Server Native Client (often abbreviated SNAC) was included in SQL Server 2005 through 2012. SQL Server Native Client can be used for applications that need to take advantage of new features introduced in SQL Server 2005 through SQL Server 2012. (Microsoft/Windows Data Access Components are not updated for these new features in SQL Server.) For new features beyond SQL Server 2012, SQL Server Native Client will not be updated. Switch to the Microsoft ODBC Driver for SQL Server or the Microsoft OLE DB Driver for SQL Server if you want to take advantage of new SQL Server features going forward.

SQL Server Native Client RDA

Came with .NET Compact Framework 3.5

ODBC Driver for SQL Server

After SQL Server 2012, the primary ODBC driver for SQL Server has been developed and released as the Microsoft ODBC Driver for SQL Server.

MSOLEDBSQL - Microsoft OLE DB Driver for SQL Server

This driver has been deprecated and later undeprecated:

The new OLE DB provider is called the Microsoft OLE DB Driver for SQL Server (MSOLEDBSQL). The new provider will be updated with the most recent server features going forward. To use the new Microsoft OLE DB Driver for SQL Server in existing applications, you should plan to convert your connection strings from SQLOLEDB or SQLNCLI, to MSOLEDBSQL. https://blogs.msdn.microsoft.com/sqlnativeclient/2018/03/30/released-microsoft-ole-db-driver-for-sql-server/

Try to use the future proof drivers:

Sql Server Odbc Driver 10 Codes

• ODBC - https://docs.microsoft.com/en-us/sql/connect/odbc/bug-fixes
• OLEDB - https://docs.microsoft.com/en-us/sql/connect/oledb/release-notes-for-oledb-driver-for-sql-server

Sql Server Odbc Driver 10 Download

Sql Server Native Client 10 Odbc Driver Download

Not the answer you're looking for? Browse other questions tagged sql-serverodbcdsn or ask your own question.