I'm in the process of setting up my first W2K3 / SQL 2000 cluster and I have a few questions with regards to MSDTC.

Documentation I have says that MSDTC must be clustered in order for SQL clustering to work. It also says that you cannot use comclust.exe anymore and that MSDTC must be setup in its own group with the following ( VIP, Network Name, and dedicated shared disk). I currently have Windows and SQL 2000 clustering up and running without MSDTC clustered.

My questions are :

1) Do I need MSDTC at all? If so, why?

2) If I do need MSDTC clustered, can I use a disk that has other applications installed on it? (I only have two LUNS to work with on the SAN, my quorum device and a device I'm using for SQL data / logs)

I know that I haven't given a lot of background information, but I was hoping I could get a discussion started.

Thanks.

Comments inline.

--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com

I support the Professional Association for SQL Server
www.sqlpass.org

"tech_arch_guy" <tech_arch_guy (AT) discussions (DOT) microsoft.com> wrote

and that MSDTC must be setup in its own group with the following ( VIP,
Network Name, and dedicated shared disk). I currently have Windows and SQL
2000 clustering up and running without MSDTC clustered.
my quorum device and a device I'm using for SQL data / logs)
recommends using another disk, but in your case the qourum drive is probably
OK. I have a cluster upgraded from W2000 to W2003 with MSDTC on the quorum
device and it works just fine.