Re: Proper procedure for adding a 3rd node to a SQL 2005/MSCS cluster
- From: "Geoff N. Hiten" <SQLCraftsman@xxxxxxxxx>
- Date: Wed, 15 Feb 2006 13:43:42 -0500
Existing node. Add-remove programs. SQL 2005.
With SQL 2000 you had to re-run the installer to change the cluster
configuration. With SQL 2005, you do cluster maintenance with add-remove
programs under control panel.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
<drew.flint@xxxxxxxxx> wrote in message
news:1140025669.304063.30830@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Right now I have a failover cluster running Windows 2003 Server
Enterprise Edition x64 and SQL Server 2005 Enterprise Edition x64. Each
node in the cluster is repsonsible for hosting a SQL Server instance.
Everything appears to be functioning correctly.
We are investigating adding a third node to provide us with N+1
failover capabilities. I have added the server into the MSCS cluster.
However, I'm stumped as far as how to get the SQL 2005 program files
installed without creating a new instance.
Could someone please advise what is the best method of adding a third
node to a cluster without having to create a third instance? Thanks in
advance,
Drew Flint
System Administrator
Plexus Systems
.
- Follow-Ups:
- Re: Proper procedure for adding a 3rd node to a SQL 2005/MSCS cluster
- From: drew.flint@xxxxxxxxx
- Re: Proper procedure for adding a 3rd node to a SQL 2005/MSCS cluster
- References:
- Proper procedure for adding a 3rd node to a SQL 2005/MSCS cluster
- From: drew.flint@xxxxxxxxx
- Proper procedure for adding a 3rd node to a SQL 2005/MSCS cluster
- Prev by Date: Proper procedure for adding a 3rd node to a SQL 2005/MSCS cluster
- Next by Date: Re: Proper procedure for adding a 3rd node to a SQL 2005/MSCS cluster
- Previous by thread: Proper procedure for adding a 3rd node to a SQL 2005/MSCS cluster
- Next by thread: Re: Proper procedure for adding a 3rd node to a SQL 2005/MSCS cluster
- Index(es):
Relevant Pages
|
