SQL Server Performance Forum – Threads Archive
the need of MSDTChey masters … we are installing a cluster with w2003 and MSDTC installation seems to be leading us to hell … or so it looks like… Tell me stupid but, what is the fundamental use of MSDTC in a SQL Server 2000 installation? is it crucial? Do I have to sleep necessarily with it?
under what circumstances could I get rid of its installation? thanks in advance!
It’s needed for any distibuted transactions that need to take place. It’s also needed if you have COM+ etc that use transactions and talk with your SQL Server. I would not get rid of MSDTC. What are the issues you are having with installing MSDTC in a win2003 cluster?
Well, I know IIS talks to MSDTC for coordinating transactions with SQL 2000, am I right? I dont know exactly if the issues arise upon installation of MSDTC, but we are installing this resource on the same group as the one we are going to use for SQL 2000 (with HP Virtual Replicator) and we dont know exactly where the problem is …
MSDTC can participate:
-Calling stored procedures on remote servers running SQL Server.
-Automatically or explicitly promoting the local transaction to a distributed transaction and enlist remote servers in the transaction.
-Making distributed updates that update data on multiple OLE DB data sources. If any of the process from SQL server involves in distributed transaction then you shouldn’t think about get rid of MSDTC as a whole. http://www.sql-server-performance.com/forum/topic.asp?TOPIC_ID=3451 by Argyle for your information. HTH Satya SKJ
This posting is provided â€œAS ISâ€ with no rights for the sake of knowledge sharing.