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 |
|
lebedev
Posting Yak Master
126 Posts |
 Posted - 2002-06-23 : 21:31:07
|
| Hi everybody.I am trying to simulate a ditributed db environment on a single machine. I know it may sound silly, but here is what I am doing:I added my SQL Server instance to itself as a linked server. I created two such linked server: DW and InfoSrc. I hoped that this would allow me to test remote (even though they reside on the same SQL server instance) stored procedure calls performed between the DW and InfoSrc servers.When an insertion is made into one of InfoSrc tables, the insertion trigger 'insTrigger' invokes a DW...dwProc, which in turn calls InfoSrc...isProc as follows:INSERT INTO #newTuplesEXECUTE InfoSrc...isProcInfoSrc...isProc just executes a simple SELECT statement.I was able to create all procedures and linked servers fine. However, when the part of DW...dwProc shown above is executed, I get the following error:Server: Msg 208, Level 16, State 1, Procedure insTrigger, Line 89Invalid object name '#newTuples'.Server: Msg 7221, Level 18, State 2, Procedure insTrigger, Line 89Could not relay results of procedure 'dwProc' from remote server 'DW'.If I run the select statement executed by InfoSrc...isProc straight from the DW...dwProc, I get the same errors plus the following:[OLE/DB provider returned message: New transaction cannot enlist in the specified transaction coordinator. ]I made sure that my DTC is turned on.Please help.thanks,Alec |
|
|
lebedev
Posting Yak Master
126 Posts |
Posted - 2002-06-25 : 18:51:01
|
I figured out the error.The problem was that I inserted into a temporary table and selected from it without actually creating it.Sorry I had to bother all 21 readers of my posting with such a noncense  |
 |
|
|
|
|
|
|
|
Link server to itself