Home Dashboard Directory Help

Linked server via MSDASQL provider fails on Timestamp column by Michael Zilberstein


 as Won't Fix Help for as Won't Fix

Sign in
to vote
Type: Bug
ID: 264309
Opened: 3/20/2007 9:53:21 AM
Access Restriction: Public
User(s) can reproduce this bug


When querying table that includes timestamp column via linked server (that works via MSDASQL provider), error returns:

Msg 7356, Level 16, State 1, Line 1
The OLE DB provider "MSDASQL" for linked server "Server1" supplied inconsistent metadata for a column. The column "TS" (compile-time ordinal 2) of object ""DBA"."dbo"."TSTest"" was reported to have a "DBCOLUMNFLAGS_ISROWVER" of 0 at compile time and 512 at run time.
Sign in to post a comment.
Posted by Microsoft on 7/28/2009 at 3:42 PM
Dear Michael,

Upon further investigation, we traced this back to a known limitation with MSDASQL ("Kagera"); see also BOL: http://msdn.microsoft.com/en-us/library/ms191462.aspx Specifically, MSDASQL reports inconsistent metadata between compile time and runtime when using a timestamp column in a remote server under these circumstances. As you correctly pointed out workarounds do exist althoug they are not perfect.

As we are deep in the release cycle for SQL 11 with no chance of a planned fix, we have closed this issue as 'by design'. How we will triage this bug in subsequent releases will depend on the urgency of a fix as requested by our customers.

Thanks for taking the time to submit a customer connect issue and please let us know if you have further questions.


Joachim Hammer
SQL Server
Posted by Microsoft on 12/20/2007 at 4:46 PM
Dear Michael,

Thanks for reporting your problem with the MSDASQL provider. We are investigating the problem and will contact you in case further action/info is needed.


Joachim Hammer

Program Manager
SQL Server
Sign in to post a workaround.
Posted by Michael Zilberstein on 3/20/2007 at 9:54 AM
Use OPENQUERY instead of 4 part name.