"Stephan" <Stephan@discussions.microsoft.com> wrote in message
news:48266C9D-90DC-418B-B3FA-9B91FA8A9E04@microsoft.com...

"Tom Moreau" wrote:

> The cluster won't restart when you add a new node. Be sure to add the SQL
> service pack to the new node while the *OLD* node owns the SQL Server
> resource. This will simply add the binaries to the new node without
> interrupting SQL. If you need to add a hotfix, however, you'll have to do
> that on the mode that owns SQL Server. Therefore, you'll have to failover
> to the new node and add the hotfix from there.
>
> --
> Tom
>
> ----------------------------------------------------
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> ..
> "Stephan" <Stephan@discussions.microsoft.com> wrote in message
> news:48266C9D-90DC-418B-B3FA-9B91FA8A9E04@microsoft.com...
> I currently have a single node SQL 2000 cluster running on 2003 Server. I
> now
> want to add the second node, but want to make sure I fully understand the
> process. I run the SQL setup from the new node and select the advanced
> option
> for failover clustering. It all seems very straight forward, but I want to
> be
> sure. Does this cause the clustered SQL instance to be restarted, or is
> there
> no outage?
>
> Any help confirming this would be appreciated.
>