Hello
I have the folowing situation on my company:

Someone configured an Active-Passive SQL 2K5 Cluster configured with only
one group!!!
This group contains all the possible resources from Cluster Service, Msdtc e
SQL (a big mistake)!!!
Now, I want and need to rearrange this cluster correctly with 3 separate
groups:

- Cluster Group
- Msdtc Group
- SQL Group

I know that rearrange the MSDTC is a easy thing, but I suppote that the step
below is almost impossible.....
Can I move all the SQL Server resources to the new group (if so, do you konw
where can I find a doc), or should I Reinstall the SQL Server on the new
Group and restore all the bds, users, etc....


Best Regards,

Bruno Ramos

Reinstall is likely your best bet. You can install a named instance, copy
the logins, them detach the databases, move the disk resources to the new
group, set the dependencies, then re-attach the database files.

You might be able to shuffle groups directly, but I wouldn't count on it not
leaving something nasty behind that bites you when you try to do something
setup related like applying a service pack or cumulative update.


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




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

Reinstall is likely your best bet. You can install a named instance, copy
the logins, them detach the databases, move the disk resources to the new
group, set the dependencies, then re-attach the database files.

You might be able to shuffle groups directly, but I wouldn't count on it not
leaving something nasty behind that bites you when you try to do something
setup related like applying a service pack or cumulative update.


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




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

Reinstall is likely your best bet. You can install a named instance, copy
the logins, them detach the databases, move the disk resources to the new
group, set the dependencies, then re-attach the database files.

You might be able to shuffle groups directly, but I wouldn't count on it not
leaving something nasty behind that bites you when you try to do something
setup related like applying a service pack or cumulative update.


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




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

Reinstall is likely your best bet. You can install a named instance, copy
the logins, them detach the databases, move the disk resources to the new
group, set the dependencies, then re-attach the database files.

You might be able to shuffle groups directly, but I wouldn't count on it not
leaving something nasty behind that bites you when you try to do something
setup related like applying a service pack or cumulative update.


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




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

Reinstall is likely your best bet. You can install a named instance, copy
the logins, them detach the databases, move the disk resources to the new
group, set the dependencies, then re-attach the database files.

You might be able to shuffle groups directly, but I wouldn't count on it not
leaving something nasty behind that bites you when you try to do something
setup related like applying a service pack or cumulative update.


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




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

Reinstall is likely your best bet. You can install a named instance, copy
the logins, them detach the databases, move the disk resources to the new
group, set the dependencies, then re-attach the database files.

You might be able to shuffle groups directly, but I wouldn't count on it not
leaving something nasty behind that bites you when you try to do something
setup related like applying a service pack or cumulative update.


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




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

Reinstall is likely your best bet. You can install a named instance, copy
the logins, them detach the databases, move the disk resources to the new
group, set the dependencies, then re-attach the database files.

You might be able to shuffle groups directly, but I wouldn't count on it not
leaving something nasty behind that bites you when you try to do something
setup related like applying a service pack or cumulative update.


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




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

Reinstall is likely your best bet. You can install a named instance, copy
the logins, them detach the databases, move the disk resources to the new
group, set the dependencies, then re-attach the database files.

You might be able to shuffle groups directly, but I wouldn't count on it not
leaving something nasty behind that bites you when you try to do something
setup related like applying a service pack or cumulative update.


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




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

Reinstall is likely your best bet. You can install a named instance, copy
the logins, them detach the databases, move the disk resources to the new
group, set the dependencies, then re-attach the database files.

You might be able to shuffle groups directly, but I wouldn't count on it not
leaving something nasty behind that bites you when you try to do something
setup related like applying a service pack or cumulative update.


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




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