MSDTC

Not 100% sure this is the right pace to post, but anyway...
We're having some problems with MSDTC. I have servers running Windows 2003
Server Standard Edition (no service packs) and each running SQL Server 2000.
We are using MSDTC to manage distributed transactions involving the
databases on these servers. The application kicks of a distributed
transaction using a class derived from ServiceComponent and then calls a
number of SQL Stored Procedures on the 3 servers. These stored procedures ca
n
access any of the 3 servers.
Most of the time this is working fine, but we seem to be getting some
intermittent problem. Looking in the MSDTC part of Componet Services, we've
noticed some transactions not resolving themselves after serveral hours. The
only way we can seem to resolve them one way or another is to kill the SQL
Server process associated with that transaction. In addition to this the siz
e
of tempdb keeps growing and only reduces once we've killed the offending
processes.
How is it that MSDTC allows these transactions to hang around for so long?I forgot to add, that when viewed in Componet Services, the stubborn
transactions appear as "INSERTEXEC (aborting)". Don't know if it relevant...
"Stevo" wrote:

> Not 100% sure this is the right pace to post, but anyway...
> We're having some problems with MSDTC. I have servers running Windows 2003
> Server Standard Edition (no service packs) and each running SQL Server 200
0.
> We are using MSDTC to manage distributed transactions involving the
> databases on these servers. The application kicks of a distributed
> transaction using a class derived from ServiceComponent and then calls a
> number of SQL Stored Procedures on the 3 servers. These stored procedures
can
> access any of the 3 servers.
> Most of the time this is working fine, but we seem to be getting some
> intermittent problem. Looking in the MSDTC part of Componet Services, we'v
e
> noticed some transactions not resolving themselves after serveral hours. T
he
> only way we can seem to resolve them one way or another is to kill the SQL
> Server process associated with that transaction. In addition to this the s
ize
> of tempdb keeps growing and only reduces once we've killed the offending
> processes.
> How is it that MSDTC allows these transactions to hang around for so long?
>
>|||Probably because they are not committed nor aborted. Use the DTC tracing
facility in Windows Server 2003 in combination with SQL Profiler and you can
see the transaction conversation.
Or get a copy of AppMetrics for Transactions from ExtremeSoft
http://www.extremesoft.com/
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright SQLDev.Net 1991-2005 All rights reserved.
"Stevo" <Stevo@.discussions.microsoft.com> wrote in message
news:19C771DC-D8A4-413A-A33E-E3F13C189FBE@.microsoft.com...
> Not 100% sure this is the right pace to post, but anyway...
> We're having some problems with MSDTC. I have servers running Windows 2003
> Server Standard Edition (no service packs) and each running SQL Server
> 2000.
> We are using MSDTC to manage distributed transactions involving the
> databases on these servers. The application kicks of a distributed
> transaction using a class derived from ServiceComponent and then calls a
> number of SQL Stored Procedures on the 3 servers. These stored procedures
> can
> access any of the 3 servers.
> Most of the time this is working fine, but we seem to be getting some
> intermittent problem. Looking in the MSDTC part of Componet Services,
> we've
> noticed some transactions not resolving themselves after serveral hours.
> The
> only way we can seem to resolve them one way or another is to kill the SQL
> Server process associated with that transaction. In addition to this the
> size
> of tempdb keeps growing and only reduces once we've killed the offending
> processes.
> How is it that MSDTC allows these transactions to hang around for so long?
>
>