It appears to have been a query issue. My working theory (so far proved correct) is that the in-memory tables @dtrs and @rawsweep were held only on the originating server....

Remote collation does not seem to be a factor. Per http://msdn.microsoft.com/en-us/library/ms190918(SQL.90,printer).aspx,

If the linked server is an instance of SQL Server, the collation information is automatically derived from the SQL Server...

Will take a look.

Here is a transaction run (again 1 row for a table, related to 202 rows for another) with time markers. Through its execution, network usage was about...

No problem.

No, I don't know if we're using remote collation. How would I find out?

I set up DTC according to this Microsoft KB: http://support.microsoft.com/kb/839279

Both servers are x86 32-bit.

The transaction ran in 1 hour 12 minutes 15 seconds and affected 203 rows of data. Will run another with timing attached.

------------------------------

2008-09-23 07:17:54.083

(1...

I must be running into a performance issue here.

I set up the DTC on two servers: the original running 2005 standard, acting as the "server". Installed 2005 express on another...

Look here: http://support.microsoft.com/kb/839279%5B/quote%5D

Thanks, will review this as well.

No, all are x86-32bit.

As far as I can tell, yes....