Install Sql Server Native Client 11.0 Odbc Driver Windows 10

  1. Install Sql Server Native Client 11.0 Odbc Driver Windows 10 Crack
-->

This article discusses the ODBC drivers that connect to SQL Server.

In SSIS 2012, our packages use an 'OLE DBSQL Server Native Client 10.0' connection to access the SQL Server 2000 databases (we actually just edited the connection strings and changed Provider from 'SQLNCLI11.1' to 'SQLNCLI10.1'). The developers had both drivers on their machines and so did the db servers we originally deployed to. Installing SQL Server Native Client 10.0. I came across an issue today where a website had a dependency on the SQL Server Native Client 10.0, which is part of SQL Server 2008. A recent upgrade to SQL Server 2012 caused SQL Server Native Client 11.0 to be installed and version 10.0 to be uninstalled. Different versions of the Native Client can.

SQL version compatibility

Compatibility indicates that a driver was tested for compatibility against existing releases of SQL at the time of the driver's release. SQL Server releases generally try to maintain backwards compatibility with existing client drivers. But new features in SQL Server releases may not be available with older client drivers.

Database version →
↓ Driver Version
Azure SQL DatabaseAzure Synapse AnalyticsAzure SQL Managed InstanceSQL Server 2019SQL Server 2017SQL Server 2016SQL Server 2014SQL Server 2012SQL Server 2008 R2SQL Server 2008SQL Server 2005
17.6YesYesYesYesYesYesYesYes
17.5YesYesYesYesYesYesYesYes
17.4YesYesYesYesYesYesYesYes
17.3YesYesYesYesYesYesYesYesYesYes
17.2YesYesYesYesYesYesYesYesYes
17.1YesYesYesYesYesYesYesYesYes
17.0YesYesYesYesYesYesYesYesYes
13.1YesYesYesYesYesYes
13YesYesYesYesYes
11YesYesYesYesYes

Connection string details

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

Install Sql Server Native Client 11.0 Odbc Driver Windows 10 Crack

The following matrix indicates driver version support for Windows operating system versions:

Operating system →
↓ Driver version
Windows Server 2019Windows Server 2016Windows Server 2012 R2Windows Server 2012Windows Server 2008 R2Windows 10Windows 8.1Windows 7Windows Vista SP2
17.6YesYesYesYesYesYes
17.5YesYesYesYesYesYes
17.4YesYesYesYesYesYesYesYes
17.3YesYesYesYesYesYesYesYes
17.2YesYesYesYesYesYesYes
17.1YesYesYesYesYesYesYes
17.0YesYesYesYesYesYesYes
13.1YesYesYesYesYesYesYes
13YesYesYesYes
11YesYesYesYes

Installing Microsoft ODBC Driver for SQL Server

The driver is installed when you run msodbcsql.msi from one of the Downloads for 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.

Side-by-side with Native Client

The driver can be installed side-by-side with SQL Server Native Client. Major versions of the driver (11, 13, 17) can all be installed side-by-side with each other, as well.

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. Here is an example.

End-user license

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. Here is an example.

Silent uninstall

The following example shows how to perform a silent uninstall.

Indicate dependency

When an application uses the driver, the application should indicate that it depends on the driver through the install option APPGUID. this indication 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. Here is an example.

Command-line tools: sqlcmd.exe and bcp.exe

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.

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.

Install sql server native client 11.0 odbc driver windows 10 crack

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:

ComponentDescription
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.hThe 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.

See also