For example, if you are using SQL Server Native Client 10.0, you can try using SQL Server Native Client 11.0 (even though, you should not be using SQL Server Native Client on new development work, as I explain further in this article). If the previous step didn’t help, another thing to try, is to make sure that you are using updated connectivity drivers. If the above solved your problem, that’s great, you are in luck.
![sql server native client 10 vs oledb sql server native client 10 vs oledb](http://2.bp.blogspot.com/-Izb0Hxslebg/Txb8gZjST-I/AAAAAAAAA6E/jS82nd5X8G0/s1600/OledbProvider.png)
Try this: SELECT * FROM OPENQUERY(, 'SELECT * FROM. The first thing to try and do, hoping that it might resolve the issue, is to use OPENQUERY in case you are using the four-part naming approach. So, if you are in a situation where you got the above message, don’t worry because there is a logical explanation about it. SQL Server Native Client, even deprecated (we will talk more about this later), it still heavily used, mostly for integrating different systems/applications with SQL Server, or even integrate different SQL Server instances via linked servers.
Sql server native client 10 vs oledb download#
SQL Server 2012 Native Client (yes, that is SQL Server Native Client 11.0 – download here), is a stand-alone data access application programming interface (API), used for both OLE DB and ODBC ( learn more). You might get the above error message, when you are trying to connect to a SQL Server instance, from another server, using SQL Server Native Client 11.0. The column “” (compile-time ordinal 1) of object “” was reported to have a Incomplete schema-error logic. This post explains the error message you might get in SQL Server: The OLE DB provider “SQLNCLI11” for linked server “” supplied inconsistent metadata for a column.