-->![Microsoft sql native client download Microsoft sql native client download](/uploads/1/2/6/4/126478234/917240869.png)
APPLIES TO: SQL Server Azure SQL Database Azure Synapse Analytics (SQL DW) Parallel Data Warehouse
![Microsoft sql server 2012 native client cannot be found Microsoft sql server 2012 native client cannot be found](/uploads/1/2/6/4/126478234/931488626.jpg)
How to install the Microsoft SQL Server Native Client (bcp.exe). First open the Server Manager tool of Microsoft Windows Server 2012 R2.
Summary
This article contains download information about the Microsoft SQL Server Native Client Drivers package. Certain Microsoft Access features do not work correctly when these drivers are not installed.
Note
The SQL Server 2012 Feature Pack is a collection of stand-alone packages that provide additional features to SQL Server 2012. The SQL Server Native Client Drivers package is a subset of the Feature Pack.
More Information
To download the SQL Server Native Client Drivers package, click the following link as appropriate for the operating system that you are running.
For the 32-bit version of SQL Server 2012:
For the 64-bit version of SQL Server 2012:
-->![Microsoft sql native client download Microsoft sql native client download](/uploads/1/2/6/4/126478234/917240869.png)
This topic discusses how various data-access components can be used with SQL Server Native Client.
Server Support
SQL Server Native Client 11.0 supports connections to, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012 (11.x), SQL Server 2014 (12.x), and Azure SQL Database.
Supported Operating System Versions
The following table lists which operating systems support SQL Server Native Client.
SQL Server Native Client version | Supported operating systems |
---|---|
SQL Server Native Client (SQL Server 2005) | Microsoft Windows 2000 Service Pack 4 or later Microsoft Windows Server 2003 or later Microsoft Windows XP Service Pack 1 or later Microsoft Windows Vista (requires SQL Server Service Pack 2, or later) Microsoft Windows Server 2008 R2 (requires SQL Server Service Pack 2, or later) |
SQL Server Native Client 10.0 (SQL Server 2008) | Microsoft Windows Server 2003 Service Pack 2, or later Microsoft Windows XP Service Pack 2, or later Microsoft Windows Vista Microsoft Windows Server 2008 R2 |
SQL Server Native Client 10.5 (SQL Server 2008 R2) | Microsoft Windows Server 2003 Service Pack 2, or later Microsoft Windows XP Service Pack 2 or later Microsoft Windows Vista Microsoft Windows Server 2008 R2 Microsoft Windows 7 |
SQL Server Native Client 11.0 (SQL Server 2012 (11.x) and SQL Server 2014 (12.x)) | Microsoft Windows Vista Microsoft Windows Server 2008 R2 Microsoft Windows 7 Microsoft Windows 8 Microsoft Windows Server 2012 |
ADO Support Policies
ADO applications can use the SQLOLEDB OLE DB provider that is included with Windows if they do not require any of the features of SQL Server 2005 (9.x) or later.
ADO applications can use the version of SQL Server Native Client included in SQL Server 2005 (9.x). ADO applications can also use SQL Server Native Client 11.0 (included in SQL Server 2014 (12.x)), but if they do so they must specify
DataTypeCompatibility=80
in the connection strings. Only features from SQL Server 2005 (9.x) are available when DataTypeCompatibility=80
is present in the connection strings.BCP Support Policies
Beginning in SQL Server 2008, bcp.exe supports data files that are no more than three SQL Server versions older than the version of SQL Server in which bcp.exe shipped.
ODBC Support Policies
Applications should use the SQL Server ODBC driver included with the Windows operating system. You can use the SQL Server Native Client ODBC driver if the application is certified it for use with a specific version of SQL Server Native Client.
OLE DB Support Policies
Applications should use the SQL Server OLE DB provider included with the Windows operating system. You can use the SQL Server Native Client OLE DB provider if the application is certified for use with a specific version of SQL Server Native Client.
OLE DB applications that have not been certified for use with SQL Server Native Client can use SQL Server Native client if they specify
DataTypeCompatibility=80
in their connection strings.OLE DB applications that use OLE DB Service Components can only use SQL Server Native client if they specify
DataTypeCompatibility=80
in their connection strings. However, no features added after SQL Server 2005 (9.x) will be available in this case.![Microsoft sql server 2012 native client cannot be found Microsoft sql server 2012 native client cannot be found](/uploads/1/2/6/4/126478234/931488626.jpg)