Hello,

I've setup Win2k3/SQL 2005 clusters in the past but I've never had to deal
with Multiple instances.

I will be installing each instance in it's own Resource group so my question
is do I need to create a MSDTC for each instance or can I have 1 MSDTC in
it's own Resource Group?

Thanks

See if this helps
http://weblogs.sqlteam.com/geoffh/ar...-Clusters.aspx


--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP



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

Hi Geoff,

Thanks for your reply. It sound's like I need to create a dedicated
Resource Group for the MSDTC and all instances of SQL will have to use that.

I think could be a performance issues as if MSDTC is on one node and a SQL
instance is on another node the Traffic could be an Issue, but time will tell
(unless you have any advice)

Interesting about Win2k8 but were not there yet

Ta!

Stu


"Geoff N. Hiten" wrote:

I am trying to find out if this is my issue:

Windows 2003 Servers SP2 (2)
Clustered
SQL 2000 SP4 (Clustered)

Trying to install a clustered instance of SQL 2K5, but when it goes through
the install process it fails on the installation on the remote node. Now I
have seen the bulletin about RDP, Task Scheduler, etc. and have tried
installation again after rebooting both nodes.

Wondering if the node I am installing this on, since it has control to the
groups of drives, is the reason why I can not get the remote system to
install since DTC can't run with the first node still holding the resources.



"Geoff N. Hiten" wrote:

If you set dependencies that interlink SQL and MSDTC, yes, you can have
problems.

Better to remove MSDTC from the SQL group, put it on the cluster group, and
then finish the installs.

You can always move it back later if MSDTC volume becomes a problem.


--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP


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

FOUND my issue after searching high and low for some resolution to WHY my SQL
2K5 cluster installation would fail when the process would try to install the
remote agent on the other node.

NOTE TO SELF AND OTHERS TO SAVE TIME AND HEADACHES

DO NOT USE A ISO IMAGE AND A VIRTUAL CD APPLICATION TO INSTALL SQL CLUSTER.


Issue appears to be that the other node was not able to actually reach the
setup files for the SQL server installation.


Yes I have been beating myself up since figuring out this was the issue.

"Geoff N. Hiten" wrote:

Just to add to a point that you noted.

You cannot be logged on to both servers at the same time when installing.
If you are, the Scheduler for whatever reason can't complete its tasks and
the install will fail. So, remember to logoff the 2nd node before installing
the cluster.

~DetRich

"myndkrime" wrote: