July 27, 2007 at 2:15 pm
Our network guys are going to set up a dummy SQL 2000 on a VMWare machine to test upgrading from 2000 to 2005. It does not have enough space to load a copy of our Production Database (almost 300 Gig). I can copy system databases, and maybe a stripped down copy of production to the VM server.
I think it would make more sense to install a separate instance of SQL2000 on our developement box and run the practice upgrade against a full copy of the Production database there, better simulating the actual process.
What are the space requirements for the upgrade ?? How much free space do I need relative to my current database size ?
Does the upgrade take longer based on the size of the DBs ??
Is there a risk to installing and upgrading a new SQL2000 instance on a box that is also in use as a developement SQL server in the existing SQL2000 INSTANCES ?? (We currently have 2 instances of SQL2000 on the developement server that are in use, and should not be disrupted)
Thanks for any thoughts and advice.
July 27, 2007 at 2:26 pm
IF your development machine has the 600+ Gig of free space to install a copy of your production Database, then create a 3rd Database instance on the test machine. Then you can install SS2k5 on the development machine and test the 'porting' over of the DB from SS2k to SS2k5.
Actual requirements for space are defined on the microsoft web site. It's always prudent to allow more than the minimum (duh), but your shop probably has its fudge factors already defined for you to use in calculations.
'Copying' the database files over from 2k to 2k5 is very easy when you are on the same machine (and same hard drive makes it easier still). IF you don't need to go back and forth on the dev machine between 2k and 2k5, you can load the 2k and verify everything is running correctly. Then you can detach from 2k, 'move' the files to their new directories [or just point 2k5 to the existing locations] and then attach the database(s) to SS 2k5.
WARNING: When you attach the database to SS2k5, the software will automatically 'update' the database to be SS2k5 compatible, rendering it unusable with SS2k.
July 27, 2007 at 2:31 pm
Currently, I have 300 Gig for the Developement DB, and another 300 Gig for a copy of the Developement DB, but I don't have any more than that.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply