-->
Oct 09, 2017 This article provides information about the updates that Microsoft is releasing to enable TLS 1.2 support for SQL Server 2017 on Windows, SQL Server 2016, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, and SQL Server.
The ODBC Driver 11 for SQL Server supports connections to SQL Server 2014, SQL Server 2012, SQL Server 2008 R2, SQL Server 2008, and SQL Server 2005 (9.x).
The ODBC Driver 11 for SQL Server on Windows can be installed on a computer that also has one or more versions of SQL Server Native Client.
The ODBC Driver 13 and 13.1 for SQL Server, in addition to the above, supports SQL Server 2016.
The ODBC Driver 17 for SQL Server supports all the above ones and also SQL Server 2017.
Microsoft® Odbc Driver 11 For Sql Server® - Windows
The ODBC Driver 17 for SQL Server supports SQL Server 2019 starting with driver version 17.3.
The driver name that you specify in a connection string is ODBC Driver 11 for SQL Server or ODBC Driver 13 for SQL Server (for both 13 and 13.1) or ODBC Driver 17 for SQL Server.
Supported Operating Systems
You can run applications with the driver on the following Windows operating systems:
- Windows Server 2008 R2
- Windows Server 2012
- Windows Server 2012 R2
- Windows Vista SP2 (ODBC Driver 11 Only)
- Windows 7
- Windows 8
- Windows 8.1
- Windows 10
Installing Microsoft ODBC Driver for SQL Server
The driver is installed when you run msodbcsql.msi from one of the following links:
- Download the Microsoft ODBC Driver 11 for SQL Server on Windows.
Note
For those who have Driver 17.1.0.1 or below installed, it is recommended that it be uninstalled manually prior to installing the newer version of the Driver
It can be installed side-by-side with SQL Server Native Client.
Microsoft Odbc Driver 11 For Sql Server : Login Failed For User
When you invoke msodbcsql.msi, only the client components are installed by default. The client components are files that support running an application that was developed using the driver. To install the SDK components, specify ADDLOCAL=ALL on the command line. For example:
Specify IACCEPTMSODBCSQLLICENSETERMS=YES to accept the terms of the end-user license if you use the /passive, /qn, /qb, or /qr option to install. This option must be specified in all uppercase letters. For example:
To do a silent uninstall:
When an application uses the driver, the application should indicate that it depends on the driver through the install option APPGUID. Doing so enables the driver installer to report dependent applications before uninstalling. To specify a dependency on the driver, set the APPGUID command-line parameter to your product code when silently installing the driver. (A product code must be created when using Microsoft Installer to bundle your application setup program.) For example:
Command-Line Tools: sqlcmd.exe and bcp.exe
Sql Server Native Client Download
The bcp.exe and sqlcmd.exe tools for use with the driver can be downloaded at Microsoft Command Line Utilities 11 for SQL Server, Microsoft Command Line Utilities 13 for SQL Server, or Microsoft Command Line Utilities 13.1 for SQL Server. The driver is a prerequisite to install sqlcmd.exe and bcp.exe.
Odbc Client Sql Server 2017
bcp.exe and sqlcmd.exe are installed in the 110Tools subfolder of %PROGRAMFILES%Microsoft SQL ServerClient SDKODBC for version 11, and 130Tools for 13 and 13.1.
An application that uses BCP functions must specify the driver from the same version which shipped with the header file and library used to compile the application.
For example, when you compile an ODBC application with msodbcsql11.lib and msodbcsql.h, use 'DRIVER={ODBC Driver 11 for SQL Server}' in the connection string.
Components of the Microsoft ODBC Driver for SQL Server on Windows
The ODBC driver on Windows contains the following components:
Microsoft Odbc Driver 11 For Sql Server Unable To Open Bcp Host Data-file
| Component | Description |
|---|---|
| msodbcsql17.dll or msodbcsql13.dll or msodbcsql11.dll | The dynamic-link library (DLL) file that contains all of the driver's functionality. This file is installed in %SYSTEMROOT%System32. |
| msodbcdiag17.dll or msodbcdiag13.dll or msodbcdiag11.dll | The dynamic-link library (DLL) file that contains the driver's diagnostics (tracing) interface. This file is installed in %SYSTEMROOT%System32. |
| msodbcsqlr17.rll or msodbcsqlr13.rll or msodbcsqlr11.rll | The accompanying resource file for the driver library. This file is installed in %SYSTEMROOT%System321033. |
| s13ch_msodbcsql.chm or s11ch_msodbcsql.chm | The Data Source Wizard help file that documents how to create a data source for the driver. This file is installed in %SYSTEMROOT%System321033 NOTE: There is no chm file for ODBC Driver 17. |
| 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 for ODBC Driver 17 or 13 is installed in %PROGRAMFILES%Microsoft SQL ServerClient SDKODBC130SDK. msodbcsql.h for ODBC Driver 11 is installed in %PROGRAMFILES%Microsoft SQL ServerClient SDKODBC110SDK. |
| msodbcsql17.lib or msodbcsql13.lib or msodbcsql11.lib | The library file needed to call the bcp utility functions that are part of the driver. Note: If you do reference this library file in your program, make sure that it is in your system path and in the system path of those that use the application. msodbcsql17.lib or msodbcsql13.lib is installed in %PROGRAMFILES%Microsoft SQL ServerClient SDKODBC130SDK. msodbcsql11.lib is installed in %PROGRAMFILES%Microsoft SQL ServerClient SDKODBC110SDK. |