Go ahead and just install shared components that would install SQL Server 2016 native client.
MSDN Support, feel free to contact is no need to install SQL 2016Īs on this server only sql native client is required. If you have any compliments or complaints to This can be beneficial to other community members reading this thread. Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. There should be shared folder.įor more details, please refer: File Locations for Default and Named Instances of SQL Server Which means, if you haven't install SQL Server 2016. Then 130 folder is used to store common files used by all SQL Server 2016 instances on a single computer. sqlncli11.dll), can continue to be utilized by SQL Server The SQL Server 2012 Native Client (v11, e.g. The latest version is SQL Server 2012 Native Client.Īlso, you can see in above link: Note that Microsoft will not be releasing a SQL Server 2014 or later version of the SQL Server Native Client.
In the 32-bit ODBC Data Source Administrator, configure an ODBC-ODBC Bridge Client data source that points to the SQL Native Client driver data source.Start the 64-bit ODBC-ODBC Bridge Server service (Easysoft ODBC-ODBC Bridge Server 圆4).Stop the 32-bit ODBC-ODBC Bridge Server service (Easysoft ODBC-ODBC Bridge Server).Install the 64-bit Windows ODBC-ODBC Bridge distribution.Īccept the Default option during Setup, which will install both the ODBC-ODBC Bridge Client and Server components.In the 64-bit ODBC Data Source Administrator (accessible from Administrative tools in Control Panel), configure a System data source for the SQL Native Client driver.
The application used is Visual Studio 2010. The ODBC driver used is the Microsoft SQL Native Client driver.
The following steps show how to access a 64-bit ODBC driver from a 32-bit application on a 64-bit Windows machine. Example: How to Connect a 32-bit Application to a 64-bit ODBC Driver ODBC calls made by your 32-bit application are passed from the 32-bit ODBC driver (the ODBC-ODBC Bridge Client) to the target 64-bit ODBC driver via the 64-bit ODBC-ODBC Bridge Server. To connect a 32-bit application with a 64-bit ODBC driver, you use a 32-bit ODBC-ODBC Bridge Client and a 64-bit ODBC-ODBC Bridge Server. A 32-bit ODBC-ODBC Bridge Client can be used with a 64-bit ODBC-ODBC Bridge Server and vice versa. The ODBC-ODBC Bridge Client communicates with the ODBC-ODBC Bridge Server by using the Remote Procedure Call (RPC) mechanism. The ODBC-ODBC Bridge Client is not linked against the ODBC-ODBC Bridge Server. The ODBC-ODBC Bridge is a client/server product. 32-bit ODBC Driver Managers can only load 32-ODBC drivers.
For this reason, 32-bit applications can only link against a 32-bit ODBC Driver Manager library. 32-bit applications must be linked against 32-bit libraries. Without the ODBC-ODBC Bridge, a 32-bit application cannot connect to a 64-bit ODBC driver. Yes, you can connect a 32-bit application to a 64-bit ODBC driver by using the ODBC-ODBC Bridge.