Does SQL 2005 in-place upgrade update all nodes?

We have a two node, single instance SQL Server 2000 cluster. If I do an
in-place upgrade to 2005, will it replace the binaries on both nodes, or must
I run the upgrade on each node?
Yes and No.
The SQL storage engine upgrade is cluster aware and will update all nodes
(assuming all nodes are online and working at the time of the upgrade). The
tools installer is NOT cluster aware and will have to be run on each node
independently. Personally, i prefer to load the tools first and then go
back and upgrade the engine.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"steveg" <steveg@.discussions.microsoft.com> wrote in message
news:963FDCFA-1752-4DBA-AA29-CAC4CFFDD705@.microsoft.com...
> We have a two node, single instance SQL Server 2000 cluster. If I do an
> in-place upgrade to 2005, will it replace the binaries on both nodes, or
> must
> I run the upgrade on each node?
sql

Does In-place upgrade set compatibility level to 9.0

This may be very obvious and when I get to the first test server I will find out, but I only have a new installation of SQL2K5 so far to test with. I have several databases that need to be upgraded to run on 2K5, but the application requires them to run in 8.0 compatibility. Does this mean that an in-place upgrade is not an option?

I apologize if this is a silly question, but I have not yet found the answer specifically.

Thanks very much.

No, it does not change the compatibility level. It leaves it at 8.0.|||

So even on an in-place upgrade you still have to go to each database and manually change the compatibility level? This tells me that it only saves me the transfer or moving of the databases themselves, right?

Thanks!

|||

Saves you moving databases, having to export/import logins from master, jobs from msdb, etc.

But it doesn't assume you want compatibility level 9.0 -and that, in my opinion, is a good thing.

Document for In-Place Upgrade of SQL Server 2000 to 2005

Hi,

We are performing the In-Place upgrade of SQL Server 2000(enterprise) to 2005(enterprise) in a clustered environment.

The issue is that the upgrade does not proceed in case both the machines in the cluster are running.

The error shown is

Product Name : Microsoft SQL Server
Product Version : 9.00.1399.06
Message Source : setup.rll
Message ID : 50000
EvtType : datastore\clustergroupsproperties.cpp@.InvokeSqlSetupDllAction@.ClusterGroupScope.SharedDisks@.0x2

It proceeds (with some errors) only if i stop the cluster service on the other machine. It is an expected behavior?

Does anyone have the documentation for this type of upgrade? Or just the basic steps to be followed.

http://www.sqlservercentral.com/columnists/ssamuel/2987.asp

http://www.microsoft.com/technet/prodtechnol/sql/2005/sqlupgrd.mspx

http://www.microsoft.com/downloads/details.aspx?FamilyID=3d5e96d9-0074-46c4-bd4f-c3eb2abf4b66&DisplayLang=en

check these links might be helpful

|||

In virtually every case of a cluster upgrade, I always tell my clients to perform a new install and not perform an in-place upgrade. If you have this option, take it. Upgrading in place is possible, but fraught with difficulties.

|||

I would need more information on your configuration and the exact steps you are going through. I wrote the section in the upgrade documentation for upgrading a cluster. I've upgraded both single instance and multi-instance clusters, in place, without any of the issues you are mentioning.

Document for In-Place Upgrade of SQL Server 2000 to 2005

Hi,

We are performing the In-Place upgrade of SQL Server 2000(enterprise) to 2005(enterprise) in a clustered environment.

The issue is that the upgrade does not proceed in case both the machines in the cluster are running.

The error shown is

Product Name : Microsoft SQL Server
Product Version : 9.00.1399.06
Message Source : setup.rll
Message ID : 50000
EvtType : datastore\clustergroupsproperties.cpp@.InvokeSqlSetupDllAction@.ClusterGroupScope.SharedDisks@.0x2

It proceeds (with some errors) only if i stop the cluster service on the other machine. It is an expected behavior?

Does anyone have the documentation for this type of upgrade? Or just the basic steps to be followed.

http://www.sqlservercentral.com/columnists/ssamuel/2987.asp

http://www.microsoft.com/technet/prodtechnol/sql/2005/sqlupgrd.mspx

http://www.microsoft.com/downloads/details.aspx?FamilyID=3d5e96d9-0074-46c4-bd4f-c3eb2abf4b66&DisplayLang=en

check these links might be helpful

|||

In virtually every case of a cluster upgrade, I always tell my clients to perform a new install and not perform an in-place upgrade. If you have this option, take it. Upgrading in place is possible, but fraught with difficulties.

|||

I would need more information on your configuration and the exact steps you are going through. I wrote the section in the upgrade documentation for upgrading a cluster. I've upgraded both single instance and multi-instance clusters, in place, without any of the issues you are mentioning.