MSDTC Resource in the 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?
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?

MSDTC Resource Group - Physical Disk and Network Name

Article 301600 (http://support.microsoft.com/?kbid=301600) mentions that
MSDTC should be in its own resource group.
- What is the recommended size for the physical disk that needs to be in
this resource group?
- Is it necessary to add the Network Name resource to DNS?
Thank you.
500 MB (meg) or bigger.
You will need an IP and Network Name for it to be on the wire.
If you are running Windows Sever 2003, be sure to follow 817064 FIRST.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog
"vkb" <vkb@.discussions.microsoft.com> wrote in message
news:48A5C66D-988B-47A1-B638-DA2FC15AEB9B@.microsoft.com...
> Article 301600 (http://support.microsoft.com/?kbid=301600) mentions that
> MSDTC should be in its own resource group.
> - What is the recommended size for the physical disk that needs to be in
> this resource group?
> - Is it necessary to add the Network Name resource to DNS?
> Thank you.

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?

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?

MSDTC and Delete transactions

Hello
I had a question reagrding MSDTC usage. I know that MSDTC will enlist
each connection transactions as it's own (take ownership) and
commit/abort accordingly.

However I'm not sure what would happen where I have a stored proc with
input parameters and 2 Delete commands on 2 different tables. In this
case, would MSDTC also enforce ACID rules when 1 cmd succeeds and 2nd
aborts ? In the script for the Stored Proc, there is no checking for
@.@.ERROR value. There are just DELETE statement and a plain RETURN.

thanks
Sunitsjoshi (sjoshi@.ingr.com) writes:

Quote:

Originally Posted by

I had a question reagrding MSDTC usage. I know that MSDTC will enlist
each connection transactions as it's own (take ownership) and
commit/abort accordingly.
>
However I'm not sure what would happen where I have a stored proc with
input parameters and 2 Delete commands on 2 different tables. In this
case, would MSDTC also enforce ACID rules when 1 cmd succeeds and 2nd
aborts ? In the script for the Stored Proc, there is no checking for
@.@.ERROR value. There are just DELETE statement and a plain RETURN.

In a normal stored procedure if you have:

BEGIN TRANSACTION
DELETE tbl WHERE ...
DELETE tbl2 WHERE ...
COMMIT TRANSACTION

you could very well end up with only one of the DELETE statements
being carried out, becuase many errors in SQL Server aborts the
current statment only.

A distributed transaction may be different. At least in some
situations there is a requirement that SET XACT_ABORT is ON. With
this settings all errors but compile errors abort the batch and
rollback the transaction.

But exactly what happens, I will have to admit that I don't know. The
best advice I can give is to test a scenario where one of the DELETE
statement fails. No, wait, the best is to either add checks on @.@.error
or make sure XACT_ABORT is ON.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx