The OLE DB provider "SQLNCLI10" for linked server "x" reported a change in schema version between compile time and run time - by Peter Edenharter

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 672153 Comments
Status Closed Workarounds
Type Bug Repros 7
Opened 6/1/2011 4:46:11 AM
Access Restriction Public


We found the folowing issue. There are 2 servers with a database. On server B there is a view "BaseTabViewLayer", that selects data via linked server from a table on server A. A second view "GetData" on Server B selects data from different sources including the view "BaseTabViewLayer".
If there is a schema change on the table on server A (in our case by a alter table disable/enable trigger) then the following error occured when calling view "GetData":
Msg 7359, Level 16, State 1, Line 1
The OLE DB provider "SQLNCLI10" for linked server "BASETAB_OLEDB" reported a change in schema version between compile time ("174775118457136") and run time ("174775118466243") for table ""SchemaChange"."dbo"."BaseTab"".

With SQL 2008 SP2 CU2 this has worked with no errors. After installing CU4 the mentioned error occured. 
Maybe this has something todo with the fix that was released with CU3.

The attached script is simplified to one database but produces the error too. 
Sign in to post a comment.
Posted by Kelvin9 on 8/12/2012 at 5:20 PM
Im seeing this on Sql 2008 R2
chain : reportserver -> view -> view -> linked server -> table
after reindex job on a weekend.
This is worked around with the workaround listed here.
Posted by AlreadyPicked on 12/21/2011 at 10:13 AM
I can confirm that the following chain : view -> linked server -> table problem is resolved with KB2498535. The following chain : view -> view -> linked server -> table still as a problem.
Posted by Satya SKJ on 10/11/2011 at 2:03 AM
As stated KB2498818 in the issue is not fixed yet, why this is shown as fixed.
Posted by cdoulis on 9/27/2011 at 12:37 PM

KB2498818 states that this bug was addressed in multiple versions (e.g., SQL 2008 R2 SP1 CU1, SQL 2008 R2 CU7) of SQL Server, but we are still experiencing the issue. Can you please make the fix available for SQL 2008 instead of having to wait for Denali?


Posted by Sherry Berry on 8/16/2011 at 2:09 PM
Can you please post when might the fix be available?
Thank you
Posted by Microsoft on 8/4/2011 at 12:52 PM
Hi Peter,
Thank you for your feedback. We have investigated the issue. The fix is currently being tested and we expect to have the fix in Denali RTM.

Pooja Harjani
Program Manager
SQL Server
Posted by Peter Edenharter on 6/23/2011 at 5:31 AM
Check after installing the security patch from 2011-06-14 (Build 4311).
The error remains unsolved.