|
|
Posted by Erland Sommarskog on 02/25/06 00:45
Altemir (david.altemir@gmail.com) writes:
> Mark's suggestion worked great when I ran it on a simple test, but I'm
> having problems applying this methodology to my real (more complex)
> application. I get the following error when running the script from
> Query Analyzer:
>
> Server: Msg 7391, Level 16, State 1, Line 1
> The operation could not be performed because the OLE DB provider
> 'SQLOLEDB' was unable to begin a distributed transaction.
> [OLE/DB provider returned message: New transaction cannot enlist in the
> specified transaction coordinator. ]
> OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
> ITransactionJoin::JoinTransaction returned 0x8004d00a].
>
> Note that both databases reside on the same server and I checked
> Distributed Transaction Coordinator (DTC) to make sure that it's
> running. What else about this kind of distributed UPDATE statement
> would cause such an error?
If the databases are on the same instance of SQL Server, there is no
need for any distributed transaction. If you get this message, you
have somehow introduced a four-part notation into the mix.
If the databases are on different instances, you need one, even if the
instance are on the same machine.
What applies to your case? What exact syntax did you use?
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Navigation:
[Reply to this message]
|