I've read the post/replies explaining how to setup MSDTC on a Windows 2003
server which is definitely great information. At this point, I still have
on problem. The KB article says that Microsoft doesn't recommend that you
create the MSDTC resource in the default Cluster Group or in the group(s)
containing the other program resources (SQL Server). What do I do if those
groups contain the only physical disk arrays that I have available?
Currently I have three (Quorum, Logs, Data). I do not have the capability
to add another physical disk array to the SAN (no drives).

Even if I could come up with another two drives (RAID-1), it seems kind of
wasteful to have only MSDTC running on them. Does anyone have any
suggestions on what the best alternative is? TIA

Travis

The recommendation is to not put MSDTC in an existing resource group. If
the only drives you have are already owned by resource groups then you do
not have any choice but to put MSDTC in one of these resource groups. The
recomendation is to help prevent drive contention.

Rand
This posting is provided "as is" with no warranties and confers no rights.

Actually, I almost always stick it into the cluster group. That might not
be best practices, but I've yet to have any issues with it.

--

Mike
Principal Mentor
Solid Quality Learning
"More than just Training"
SQL Server MVP
http://www.solidqualitylearning.com
http://www.mssqlserver.com

http://support.microsoft.com/?kbid=301600

Notice the revision date at the bottom!

Cheers,

Rod
"Michael Hotek" <mhotek (AT) nomail (DOT) com> wrote

I know, but hundreds of these in production running with DTC in the cluster
group and none of them are having any issues. Several of those clusters get
literally pounded with activity.

The article says you shouldn't do it because of best practices. It doesn't
say something is going to break if you do and since I've had dozens of
clusters configured and running that way since Beta 2/3 of Windows 2003 with
no problems, then they won't get changed unless there is going to be some
specifically documented fault which can occur along with the situation that
can cause it.

--
Mike
Principal Mentor
Solid Quality Learning
"More than just Training"
SQL Server MVP
http://www.solidqualitylearning.com
http://www.mssqlserver.com