Re: Upgrade 2000 to 2005
- From: "Kevin3NF" <kevin@xxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 17 Jan 2007 07:01:55 -0600
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
.
- Follow-Ups:
- Re: Upgrade 2000 to 2005
- From: Geoff N. Hiten
- Re: Upgrade 2000 to 2005
- References:
- Upgrade 2000 to 2005
- From: Kevin3NF
- Upgrade 2000 to 2005
- Prev by Date: Re: BCV's on a cluster
- Next by Date: Re: BCV's on a cluster
- Previous by thread: Upgrade 2000 to 2005
- Next by thread: Re: Upgrade 2000 to 2005
- Index(es):
Relevant Pages
|
Loading