MSDTC in Cluster Group

Why is it a bad idea to have the MSDTC Resource in the Cluster Group, even if
the MSDTC has its own IP Address and Network Name?
In my planned multiple instance sql cluster, I can see giving up a physical
disk to the Quarum, but another disk to MSTDC as well. Since the MSTDC
doesn't use tons on disk space, can I put it in the same group as the defualt
instance of SQL, again as long has it has its own IP Address and Network
Name?
The original MS KB posts recommended using the Cluster Group resource;
however, we've found out that it does not work and an instance of SQL Server
can not bind to it unless it's on the same node.
You can put it in the SQL Server Group resource, but it won't work once you
go multi-instanced. At that point, MS recommends that you create a seperate
shared disk resource with its own IP and Network Name resources and cluster
MS DTC as a seperate group. Looks like the coders didn't think through the
implications of the Quorum and coded against it. The SQL Server
developement group did not realize this.
Sincerely,
Anthony Thomas

"Wayne" <Wayne@.discussions.microsoft.com> wrote in message
news:922FDA87-A645-43C7-8442-BAD97525A3F1@.microsoft.com...
Why is it a bad idea to have the MSDTC Resource in the Cluster Group, even
if
the MSDTC has its own IP Address and Network Name?
In my planned multiple instance sql cluster, I can see giving up a physical
disk to the Quarum, but another disk to MSTDC as well. Since the MSTDC
doesn't use tons on disk space, can I put it in the same group as the
defualt
instance of SQL, again as long has it has its own IP Address and Network
Name?