If all of the above cannot help, then it’s time to further discuss this in order to better evaluate the situation. Why do you get the “…supplied inconsistent metadata for a column.” error? Something else you can try, if you have the luxury and the required approved downtime of course, is to reboot the server onto which you are trying to use the SQL Server Native Client ( not the database server itself!).
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. 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 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. Otherwise, the default set of exclusions from SQL Server will regenerate and the issue will remain.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. For detailed information about exclusions for Microsoft SQL Server, see the following article (section Directories and file name extensions to exclude from virus scanning and Processes to exclude from virus scanning)Īutomatic exclusions should not be enabled after making these changes. Specify new file exclusions and processes exclusions manually. Remove the existing exclusions for Microsoft SQL Server. The actual exclusion sets will remain, but they will not regenerate automatically.
In ESET File Security for Microsoft Windows Server, disable automatic exclusions. You can also disable these messages from appearing in your Application Event Log. If you are receiving these messages, you can choose to ignore them since they do not represent an issue for your system.
Refer to the Update Center for Microsoft SQL Server for the list of latest updates. We recommend that you always keep your Microsoft SQL Server up-to-date with the latest Service Pack and Cumulative Update.