Hi Guys,
rirht now my databases running on two seperate sql servers
server1 and server2 and ecah having MSDTC .
Now i am planning to shift these two servers into a
cluster.
1)shall i go for active/passive or active/active.
2)if active/active then it will be named virtual instance
will it require any modification in the application other
than changing the connection string.
3)in any case how MSDTC will get affected in the new
cluster.
4) how sql server will identify the MSDTC AS it is having
different network name, ip address tec
pls advice.
Answers inline...
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://www.msmvps.com/clustering - Blog
"Bijupg" <anonymous@.discussions.microsoft.com> wrote in message
news:173e01c51e37$f62aecd0$a501280a@.phx.gbl...
> Hi Guys,
> rirht now my databases running on two seperate sql servers
> server1 and server2 and ecah having MSDTC .
> Now i am planning to shift these two servers into a
> cluster.
> 1)shall i go for active/passive or active/active.
Do your databases require the complete power of the current machines? Will
the clustered machines be the same power or more powerful then the current
machines? What about current RAM and clustered RAM?
> 2)if active/active then it will be named virtual instance
> will it require any modification in the application other
> than changing the connection string.
You can only have one default instance in a SQL cluster. If you need two
instances, at least one will be named.
> 3)in any case how MSDTC will get affected in the new
> cluster.
MSDTC will be shared. Follow 817064 and then 301600.
> 4) how sql server will identify the MSDTC AS it is having
> different network name, ip address tec
> pls advice.
>
That is all part of the SQL magic and clustering. Ok, so I have no idea, but
I know it works well
|||As for your MSDTC here is the basic best pratice on this
When clustering MS DTC it is preferred to have it in its own group with its
own resources, your second choice should be to put it in the cluster group,
use the quorum disk and create MS DTC its own Network Name and IP Address
resources for your MSDTC resource to use and set that resources properties
not to affect the group.
Here are some KB articles on correctly setting this up:
301600 How to configure Microsoft Distributed Transaction Coordinator on a
http://support.microsoft.com/?id=301600
817064 How to enable network DTC access in Windows Server 2003
http://support.microsoft.com/?id=817064
Also this article which may be of interest:
817065 How To Enable Network COM Access in Windows Server 2003
http://support.microsoft.com/?id=817065
Dave Whitney
SQL Support
Saturday, February 25, 2012
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment