System Requirements, Installation, and Driver Files

System Requirements, Installation, and Driver Files

 

DownloadDownload ODBC Driver

The ODBC Driver 11 for SQL Server supports connections to SQL Server 2014, SQL Server 2012 R2, SQL Server 2008 R2, SQL Server 2008, and SQL Server 2005.

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 (Preview) for SQL Server in addition to the above, supports SQL Server 2016 (Preview).

The driver name that you specify in a connection string is ODBC Driver 11 for SQL Server (or ODBC Driver 13 for SQL Server if using ODBC Driver 13).

You can run applications with the ODBC driver on Windows on the following Windows operating systems:

  • Vista SP2

  • Windows Server 2008 R2

  • Windows Server 2012 R2

  • Windows 7

  • Windows 8

In addition, if using Microsoft ODBC Driver 13 (Preview) for SQL Server, Windows 10, SQL Server 2014, and SQL Server 2016 (Preview), are supported.

The ODBC Driver 13 (Preview) for SQL Server on Windows is installed when you run msodbcsql.msi from Download the Microsoft ODBC Driver 13 (Preview) for SQL Server on Windows. The ODBC driver can be installed side-by-side with SQL Server Native Client.

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 ODBC driver. To install the SDK components, specify ADDLOCAL=All on the command line. For example:

msiexec /i msodbcsql.msi ADDLOCAL=ALL  

By default the ODBC driver installer only installs the client components. To install all components (client and the SDK components), specify ADDLOCAL=All on the command line. For example:

msiexec /i msodbcsql.msi ADDLOCAL=ALL  

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:

msiexec /quiet /passive /qn /i msodbcsql.msi IACCEPTMSODBCSQLLICENSETERMS=YES ADDLOCAL=ALL  

To do a silent uninstall:

msiexec /quiet /passive /qn /uninstall msodbcsql.msi  

When an application uses the ODBC driver, the application should indicate that it depends on the driver through the install option APPGUID. Doing so enables the ODBC driver installer to report dependent applications, before uninstalling. To specify a dependency on the ODBC driver, set the APPGUID command-line parameter to your product code when silently installing the ODBC driver. (A product code must be created when using Microsoft Installer to bundle your application setup program.) For example:

msiexec /i msodbcsql.msi APPGUID={ to be determined }  

The ODBC Driver 11 for SQL Server on Windows is installed when you run msodbcsql.msi from Download the Microsoft ODBC Driver 11 for SQL Server on Windows. The ODBC driver can be installed side-by-side with SQL Server Native Client.

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 ODBC driver. To install the SDK components, specify ADDLOCAL=All on the command line. For example:

msiexec /i msodbcsql.msi ADDLOCAL=ALL  

By default the ODBC driver installer only installs the client components. To install all components (client and the SDK components), specify ADDLOCAL=All on the command line. For example:

msiexec /i msodbcsql.msi ADDLOCAL=ALL  

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:

msiexec /quiet /passive /qn /i msodbcsql.msi IACCEPTMSODBCSQLLICENSETERMS=YES ADDLOCAL=ALL  

To do a silent uninstall:

msiexec /quiet /passive /qn /uninstall msodbcsql.msi  

When an application uses the ODBC driver, the application should indicate that it depends on the driver through the install option APPGUID. Doing so enables the ODBC driver installer to report dependent applications, before uninstalling. To specify a dependency on the ODBC driver, set the APPGUID command-line parameter to your product code when silently installing the ODBC driver. (A product code must be created when using Microsoft Installer to bundle your application setup program.) For example:

msiexec /i msodbcsql.msi APPGUID={0CC618CE-F36A-415E-84B4-FB1BFF6967E1}  

The bcp.exe and sqlcmd.exe tools for use with the Microsoft ODBC Driver 11 for SQL Server on Windows can be downloaded at Download bcp and sqlcmd for the Microsoft ODBC Driver 11 for SQL Server on Windows. The ODBC driver is a prerequisite to install Sqlcmd.exe and Bcp.exe.

Bcp.exe and sqlcmd.exe are installed in %PROGRAMFILES%\Microsoft SQL Server\Client SDK\ODBC\110\Tools.

An application that uses BCP functions must specify the driver from the same version that shipped with the header file and library used to compile the application.

For example, when you compile an ODBC driver application with msodbcsql11.lib and msodbcsql.h, use "DRIVER={ODBC Driver 11 for SQL Server}" in the connection string.

The ODBC driver on Windows contains the following components:

ComponentDescription
msodbcsql13.dllThe dynamic-link library (DLL) file that contains all of the driver's functionality. msodbcsql13.dll is installed in %SYSTEMROOT%\System32.
msodbcsqlr13.rllThe accompanying resource file for the driver library. msodbcsqlr13.rll is installed in %SYSTEMROOT%\System32\1033.
s13ch_msodbcsql.chmThe Data Source Wizard help file that documents how to create a data source from the ODBC Driver for SQL Server. s13ch_msodbcsql.chm is installed in %SYSTEMROOT%\System32\1033
msodbcsql.hThe header file that contains all of the new definitions needed to use the ODBC Driver for SQL Server on Windows.

 Note: You cannot reference msodbcsql.h and odbcss.h in the same program.

msodbcsql.h is installed in %PROGRAMFILES%\Microsoft SQL Server\Client SDK\ODBC\110\SDK.
msodbcsql13.libThe library file needed to call the bcp utility functions that are part of the ODBC Driver for SQL Server on Windows.

 Note: If you do reference msodbcsql13.lib in your program, make sure that msodbcsql13.dll is in your system path and in the system path of those that use the application.

msodbcsql13.lib is installed in %PROGRAMFILES%\Microsoft SQL Server\Client SDK\ODBC\110\SDK.

The ODBC driver on Windows contains the following components:

ComponentDescription
msodbcsql11.dllThe dynamic-link library (DLL) file that contains all of the driver's functionality. msodbcsql11.dll is installed in %SYSTEMROOT%\System32.
msodbcsqlr11.rllThe accompanying resource file for the driver library. msodbcsqlr11.rll is installed in %SYSTEMROOT%\System32\1033.
s11ch_msodbcsql.chmThe Data Source Wizard help file that documents how to create a data source from the ODBC Driver for SQL Server. s11ch_msodbcsql.chm is installed in %SYSTEMROOT%\System32\1033
msodbcsql.hThe header file that contains all of the new definitions needed to use the ODBC Driver for SQL Server on Windows.

 Note: You cannot reference msodbcsql.h and odbcss.h in the same program.

msodbcsql.h is installed in %PROGRAMFILES%\Microsoft SQL Server\Client SDK\ODBC\110\SDK.
msodbcsql11.libThe library file needed to call the bcp utility functions that are part of the ODBC Driver for SQL Server on Windows.

 Note: If you do reference msodbcsql11.lib in your program, make sure that msodbcsql11.dll is in your system path and in the system path of those that use the application.

msodbcsql11.lib is installed in %PROGRAMFILES%\Microsoft SQL Server\Client SDK\ODBC\110\SDK.

Microsoft ODBC Driver for SQL Server on Windows

Community Additions

ADD
Show:
© 2016 Microsoft