Creating a Cross Server View

  • Hi,

    I am trying to create a View that pulls data from databases on 2 servers (1 SQL 2000 and 1 SQL 2005), but when I try and save the view I get the following error, I have checked and the query runs with no problems. I can using a Linked Server which is setup using the SQL Server OLE DB Provider, does anyone have any ideas how I can fix this.

    ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]The operation could not be performed because the OLE DB provider 'SQLOLEDB' was unable to begin a distributed transaction.

    [Microsoft][ODBC SQL Server Driver][OLE/DB provider returned message: New transaction cannot enlist in the specified transaction coordinator.]

    [Microsoft][ODBC SLQ Server Driver][SQL Server[OLE DB error trace [OLD/DB Provider 'SQLOLEDB' ITransactionJoi JoinTransaction returned 0x800400a].

    Thanks,

    Gavin,

  • Where is the reference to Transactions coming from in the error message? Are you by any chance using Transactions?


    Regards,

    goodguy

    Experience is a bad teacher whose exams precede its lessons

  • Hi,

    I was initially trying to create a complex view and having the errors, so I did a quick test which was a very simple View on the SQL 2000 server which was:

    SELECT * FROM SQL2005Server.DITA.dbo.EnrolmentAll

    This was created on the SQL 2000 Server and when it is run it works fine, but as soon as you try to save the view it comes up with the above error.

    I have tried doing the reverse and creating a view on the SQL 2005 Server which references the SQL 2000 Server and this saves with no problems, so the problem seems to be from 2000 to 2005.

    Thanks,

    Gavin,

  • I haven't worked with SS2005, but it does make sense that SS2K will not be as capable of linking up with SS2005 as vice versa, so I'm glad you've managed to solve your problem.


    Regards,

    goodguy

    Experience is a bad teacher whose exams precede its lessons

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply