MSDTC in Cluster SQL2k

#1

I currently support this configuration (Win2K A/S SP3,
SQL2K E/E SP2)(Compaq DL580 - 4Proc - 8GB RAM).

And have worked with PSS to resolve issues I have
experienced regarding moving the MS DTC resources to
another group.

Basically, I agree, if you are not experiencing any issues
(Performance or otherwise) with the MS DTC in the default
configuration - Don't Change it! And why would you want
to?

We currently have the cluster group with the Quorum, MS
DTC, cluster Ip and cluster name resources in it. And for
the SQL resource Group we have the Logs drive, Data drive,
SQL IP, SQL name, and the SQL Server, AGent and Fulltext
resources(Plus a couple custom resources(application and
services)).

When one of the SQL resources fails the cluster will move
the SQL resources to the passive node. This is normal
operation. But what we have is the cluster group on one
node and the SQL group on the other node. If any of your
SQL logic depends on the MS DTC, they will fail because
they are not local to the node that owns the SQL Resources.

We moved the MS DTC to the SQL group. What this
effectively accomplishes is moving all resources under one
group so that if one resource fails all the resources fail
to the passive node. This works for us and although it is
not a MS "Best Practice" it is supported by Microsoft.

The process is painless, just right click the MS DTC
resource and Click 'Change Group' and select the group you
want to move it to. There will be a message that will
verify moving all dependent resources with it and click
yes to complete the move. I tested this in the lab and am
ready to deploy it in production.

I hope this helps,
Chris

Quote:

-----Original Message-----
Best option is to leave the way it is as it works fine.
Re. KB they are confusing and i'm right now ignoring it
for good unless they post particular scnarios when
we need to do it.

-----Original Message-----
Here is an excerpt from MS support.microsoft.com/
webcast
from SQL/Clustering Expert (hope this helps):
"Well first off, it's preferred to leave it in its
default
location, which in Windows® 2000 is going to be in the
Cluster directory. If you have a concern about MS DTC
affecting the cluster and causing a shut down, you can
take the MS DTC resource off line, go to its properties
and set it not to affect the rest of the group. That
would
be the preferable thing to do. MS DTC for older
installations where there previously was a 6.5 or 7.0
SQL
Server installed, is probably going to have the MS DTC
resource in the SQL group so that when you unclustered
it,
did your upgrade to 2000, and then reclustered it, it is
still there. That is okay also. We just really prefer
that
you do not move the resource.

There are KB articles out there documenting how to move
the resource. You're also going to see articles out
there
recommending that nothing be in the Cluster group. MS
DTC
is going to be the exception to that and one of the big
problems with moving MS DTC is that, if it's not done
correctly and we have to repair it, you're going to have
your whole cluster down. So if you have other things
running on the cluster, everything is out, not just this
one SQL Server, but the whole cluster is going to down
while we repair the MS DTC, which is more than likely
going to cause us to have to remove it and reinstall it.
This may or may not be a painful experience. So the
general rule is just leave it where it is, let it do its
job, and do not move it. The only other reason for
moving
it would be some legacy applications are expecting to
find
it in a particular group, in which case you will have to
do that."
-----Original Message-----
I am confused about the proper way to configure MSDTC
on
a
cluster. I have read 290624 and 294209, but quite
frankly,
it is unclear as to whether MSDTC should be assigned a
unique ip address and its own network name or not.

Envrionment: Windows 2000 Advanced Server, SQL 2000
Enterprise Edition SP3

Right now the MSDTC resource (by default) is in the
Cluster Group, and the Dtclog is on the Quorum drive,
and
it's working. And, Microsoft seems to say in several
places that if it is installed there and it is working
then leave it there. Is that really the recommended
approach? Should it really be there? Or is it better to
put it with SQL, or even better yet in a group all by
itself?

If I put it in the same group as SQL Server can MSDTC
just
use the ip-addr and network name for SQL Server or does
it
really need its own?If I put MSDTC in SQL group are
there
any disadvantages?

If I put it in its own group, all by itself it would
have
to have a unique ip address and a network name and its
own
little disk. Is this the best thing to do?

It would be simpler if there were no choice.
Thanks,
--Jp
.

.

.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

MSDTC in Cluster SQL2k

microsoft.public.sqlserver.clustering microsoft.public.sqlserver.clustering

MSDTC in Cluster SQL2k - 07-08-2003 , 02:18 PM