May 13, 2010 at 11:57 pm
Hi,
We are in urge for migrating sql 2000 to sql 2008.
On what basis we can make a choice between In-Place Upgrade and Side-By-Side Upgrade?
I personally felt that side-by-side is the best way to do the migration rather ending up in re-installing the sql server in doing a IN-PLACE upgrade.
Would like to know which method does microsoft suggests/recommends and what factors we need to consider for going either of the methods.
Thanks in Advance.
May 14, 2010 at 12:36 am
Unless your 2000 server is fairly new you are likely buying new hardware for the 2008 box. The is a very common case for an upgrade. Although an in-place upgrade is supported it has always left me feeling a little anxious. What happens if we get halfway through and it bombs out and I can't get SQL 2000 back up.. Given the risks the ONLY case I find an in-place upgrade palatable is when no other hardware is available.
Using the side-by-side method you have both your old and new servers and if you need to rollback to your old server it is pretty painless..
CEWII
May 14, 2010 at 3:01 am
Thanks.
May 18, 2010 at 6:44 pm
We are going through the same assessment for our production systems, however we are going from SQL 2005 to 2008. Our hardware is pretty beefy as we upgraded it last year via migration and split the Web server/Report server from the back end database. I'm hesitant to do a migration because of the expense in leasing another set of hardware (we use a 3rd party host) for some overlapping time period while we do the migration, plus we would have to set up the new hardware from scatch. This takes up a lot of time and means that we have to test everything instead of just our database apps. The only way that migration makes sense for us is if we can image the existing system and drop the image on the new hardware. Otherwise I'd rather just do some test runs of an inplace upgrade on our test box and have a fully tested back out plan if the upgrade doesn't work. The back out steps would be along the lines of uninstalling SQL 2008, reinstalling 2005 and applying the 2005 versions of the database backups. We are lucky in that we can have a weekend of planned outage without an issue. If not, then a migration would be necessary, however you then have the complication of having to keep all your data current with production.
All in all it's a big project and although I really want to use the 2008 features (especially in SSRS), I'm not looking forward to it.
MWise
May 18, 2010 at 9:25 pm
Thanks for the suggestions and sharing your experience.
May 18, 2010 at 9:41 pm
In a lot of ways I'm a lot more comfortable with an in-place upgrade from 2005 to 2008. I'm not sure I could quantify exactly why but the jump from 2000 to 2005 involves so much new tech and new services where as 2005 to 2008 doesn't really feel that big. Sorry I can't quantify it..
CEWII
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply