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?
It's more a matter of usage and availability. If you use it a lot, even
though its small, it takes it toll on the disk. You would never want MSDTC
to take cycles away from what the quorum is trying to use. As for
availability, what happens if you have a resource failure? By default, the
group is afftected. Putting more things in ANY group, affects the group as a
whole. For the Highest Availability, keep everything separate.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog
"Wayne" <Wayne@.discussions.microsoft.com> wrote in message
news:E91F75E1-1006-4062-8BC7-35D94FD3E77F@.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?
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment