Our calls to a component are taking a long time and sometimes timing out when the calls are done inside of MTS.
The same methods execute immediately when run outside of MTS.
I have debugged it and found where the big performance hit is.
cmd.Execute is the first one. It takes about 20 seconds.
And the "End Function" line on the method also takes about 20 seconds.
I believe (though maybe incorrectly) that it looks like MTS is having a problem beginning and committing the transactions, due to the locations of the performance hits.
The stored proc just deletes things from about seven tables and returns.
I can begin a transaction and commit it in in ISQL and I can begin a distributed transaction and commit it in ISQL with no problem.
We are using MTS with a VB6 component which is set to require transactions.