Re: Upgrade 2000 to 2005

The nodes are about 3 months old. Not sure about the SAN. This place
leases hardware IIRC, so that would not be an issue.

Testing the restore is of course part of the plan :) but I always appreciate
the reminder...

Still hoping to see if anyone has direct experience with imaging the nodes
of the cluster and usnig that image as a restore....

--
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm

Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com


"Edwin vMierlo" <EdwinvMierlo@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:eubG506OHHA.3268@xxxxxxxxxxxxxxxxxxxxxxx
I agree, I am not a big fan of upgrading clusters either, but I realise
sometimes there is no choice.
Ensure you have a *proven* backup and restore procedure, and backup prior
to
your upgrade.
(*proven* = actually tested, else you might be in for a disaster)

Is your hardware still under warrantee / support ?
And for how long ?
( it might be time to think of building a new cluster with new
hardware... )



"Geoff N. Hiten" <SQLCraftsman@xxxxxxxxx> wrote in message
news:u3hdLb2OHHA.4104@xxxxxxxxxxxxxxxxxxxxxxx
I have never been a big fan of a cluster upgrade. The rollback plan
basically becomes uninstall, reinstall, reload from backup. As a safety
measure, I would detach the user databases, upgrade in place, and then
attach. That way, if there is a failure in the upgrade process, you at
least save the restore step.

--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP




"Kevin3NF" <kevin@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:uF8ZqejOHHA.1240@xxxxxxxxxxxxxxxxxxxxxxx
New instance requires disk resources. I don't have disk resources
available. Or is 2005 that much different...

--
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm

Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com


"Zekske" <Zekske@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:14036779-7155-491E-AEB6-E431A07E05BF@xxxxxxxxxxxxxxxx
Never did a cluster upgrade yet but I can tell you that images of
clusternodes work.
What you also can do is install SQL 2005 as a new instance aside your
SQL2000.
Then you can migrate your database from 2000 to 2005 keeping your old
databases as rollback and without the need of new hardware

"Kevin3NF" wrote:

Gentlemen, geniuses, either or both....

My client has a multi-instance SQL 2000 SP3 (.818) cluster on Win2K3.

He wants to upgrade both instances to 2005. Cool.

No extra drives/luns/whatever the proper term is are available in the
SAN.

Am I stuck with an in place upgrade? I would have preferred to do a
side by
side and move the databases but the hardware just aint there.

In this situation, what you do from a "rollback" perspective in case
he
upgrade blows chunks and has to revert? For a standalone, I assume
imaging
software would work...would a cluster image work just as well?

2005 upgrades are something I just haven't touched yet...:(

Thanks!

--
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm

Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com











.

Relevant Pages

  • Re: SQL Server 2005 and file systems, any recommendations
    ... I had to travel to customer to perform a triple upgrade: ... Had the databases been on plain files, the OS upgrade would have been ... since buffering in the file system could cause problems. ... Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx ...
    (comp.databases.ms-sqlserver)
  • Re: Sort Order not as I planned
    ... I have an important customer who has upgraded to SQL Server 2005 with 9 ADP ... databases I have designed for them. ... This upgrade was done for replication purposes for other SQL Server ... Sylvain Lafontaine, ing. ...
    (microsoft.public.access.adp.sqlserver)
  • Re: Upgrade 2000 to 2005
    ... I would not due an in-place upgrade; they are dirty and they never end up ... So, given your hardware restrictions, here is the tact I would take. ... completely uninstall the SQL 2000 installation. ... Real-world stuff I run across with SQL Server: ...
    (microsoft.public.sqlserver.clustering)
  • Re: Update MSDE2000 to SQL2000 on same server
    ... Yes you do an upgrade from MSDE to SQL 2000 Enterprise. ... a full database backup of all databases. ... Step 2 Click SQL Server 2000 Components. ...
    (microsoft.public.sqlserver.setup)
  • Re: Upgrading from 6.5 to 2005
    ... We learned from Microsoft's "SQL Server 2005 Implementation and ... Maintenance - Self-Paced Training Kit" that there is no direct upgrade path ... we have both 2000 and 2005 evaluation versions installed on a new ... databases when they are in 2000. ...
    (microsoft.public.sqlserver.setup)
Loading