March 5, 2012 at 12:51 am
can i upgrade sql server 2000 sp2 to sql sevrer 2005 in inplace upgrade?
or
from server 2000 sp4 to server 2005 only possible
what i studied is this one
only 2000 sp4 to 2005 sp4 to 2008.
but after reading some articles i got confusion....
and
is it same way for side by side also ??
thanks
March 5, 2012 at 5:15 am
s1123 (3/5/2012)
orfrom server 2000 sp4 to server 2005 only possible
what i studied is this one
only 2000 sp4 to 2005 sp4 to 2008.
but after reading some articles i got confusion....
and
is it same way for side by side also ??
thanks
I would not suggest doing an InPlace upgrade. Don't you have new hardware for your SQL Server 2005?
March 5, 2012 at 3:06 pm
I did in place upgrades from 2000 to 2005 without problems, but I'm pretty sure I was on the most recent 2000 service pack first. I don't know if it matters.
March 5, 2012 at 3:22 pm
You need to be on SP3 or later for SQL Server 2000, please see the following links
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
March 5, 2012 at 8:56 pm
thanks guys
thanku perry, thats really helpful
and
i got another doubt guys..
i can upgrade SQL Server 7.0 Enterprise Edition SP4 to SQL Server 2005 .
does it mean, the inplace upgrade has been introduced from SQL Server 2005??
and
what about side by side can i use SQL Server 7.0 and SQL Server 2005??
March 6, 2012 at 12:00 am
You can run sql7 or SQL 2000 side by side with 2005 or even 2008, but there are ramifications especially when it comes to uninstalling the previous instances. Personally I wouldnt run them together. This linkhas some detail
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
March 6, 2012 at 7:31 am
Doing any upgrade in place between SQL Server versions has risks.
Your plan needs to include what you will do if the upgrade fails part way through and SQL Server cannot be started. (Hint - the only working upgrade path for this is a side-by side upgrade.)
You need to balance risk, cost and downtime. IMHO the option that gives the lowest risk, cost and downtime is side by side.
Before running any upgrade, check out your system with the Upgrade Advisor. Then build a test system with the new version and test everything.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply