Re: UPDATE Statement Involving Tables in Different Databases
- From: "Altemir" <david.altemir@xxxxxxxxx>
- Date: 24 Feb 2006 12:09:34 -0800
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?
.
- Follow-Ups:
- Re: UPDATE Statement Involving Tables in Different Databases
- From: Erland Sommarskog
- Re: UPDATE Statement Involving Tables in Different Databases
- References:
- UPDATE Statement Involving Tables in Different Databases
- From: Altemir
- Re: UPDATE Statement Involving Tables in Different Databases
- From: markc600
- UPDATE Statement Involving Tables in Different Databases
- Prev by Date: Re: Fields in my tables are disappearing!
- Next by Date: Re: Subquery -> slowness
- Previous by thread: Re: UPDATE Statement Involving Tables in Different Databases
- Next by thread: Re: UPDATE Statement Involving Tables in Different Databases
- Index(es):
Relevant Pages
|