Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
LOOKUP_BI
Constraint Violating Yak Guru
295 Posts |
 Posted - 2008-07-29 : 11:13:00
|
| Hi ,I encountered the following error mssgThe OLE DB provider "SQLNCLI" for linked server "X" reported a change in schema version between compile time ("A") and run time ("B") for table ""database"."schema"."tablename"".Anyone knows what steps I can take to resolve this problem? |
|
|
LOOKUP_BI
Constraint Violating Yak Guru
295 Posts |
Posted - 2008-07-29 : 12:05:46
|
Should I recreate the linked server or the synonym ?quote:
Originally posted by LOOKUP_BI
Hi ,I encountered the following error mssgThe OLE DB provider "SQLNCLI" for linked server "X" reported a change in schema version between compile time ("A") and run time ("B") for table ""database"."schema"."tablename"".Anyone knows what steps I can take to resolve this problem?
|
 |
|
|
LOOKUP_BI
Constraint Violating Yak Guru
295 Posts |
Posted - 2008-07-29 : 13:11:51
|
| I have got a solution for the problem. I am thinking that when i ran the same query the day before, it somehow caches the query and when the new one is run, it somehow goes back and refer to the "expired" query. When I run the sp_recompile, it is running well. Also, I tried DBCC FREESESSIONCACHE WITH NO_INFOMSGS. This one also works!But:1. What is the real reason causing this schema issue?2. I can run this every time it has the problem, but this is not a professional solution. How can take care of this so that I will not face the same problem tomorrow when it needs to run again? |
|
|
|
|
|
|
Synonym Prob on SQL 2005