Avatar of santaspores1
Flag for United States of America asked on

32-bit SQL Server 2000 Database to 64-bit 2008 server


I have a new server.  It acts as a web application server (asp.net) with an sql database back end.

The new server is 64-bit Windows Server 2008 R2 and I have installed 64-bit SQL Server 2008 R2.  I need to migrate databases that currently reside on a 32-bit Windows Server 2003 box running 32-bit SQL server 2000.  I plan on using the backup and restore method.  It looks like (from what I have read so far) I shouldn't encounter any real problems.  

I thought I would have to use transact SQL (specifying WITH MOVE) rather than a wizard because the data and log file paths on my new server will be different than on the old server - but it looks like the restore wizard on the 2008 box will move the files to the proper location rather than creating the old path from the old server.  It looks to me that the "resore the database file as" option takes care of that.  The defualt value there was:
C:\MyApps\SQL Server 2008 R2 64-bit\MSSQL10_50.MSSQLSERVER\MSSQL\Data\MyDatabaseName.MDF
Note that when I installed SQL server 2008 it wanted two paths - a 32-bit path (which defaulted to something like C:\Program Files\SQL Server (x86) ) and a 64-bit path (which defaulted to something like C:\Program Files\SQL Server)
It looks like the data files are being installed to the 64-bit path.

So Question 1 is:  Can I use the GUI as above to restore the database?  Does the "resore the database file as" location option take care of the "WITH MOVE" option (the WITH MOVE wording does not appear in the GUI Wizard as such)

Question 2 is: Also, when installing SQL server 2008 R2, it created TWO application paths - one for 32-bit and one for 64-bit.  The server management Studio is in the 32-bit path... is there not a 64-bit server management studio?

Microsoft SQL Server 2008ASP.NET

Avatar of undefined
Last Comment

8/22/2022 - Mon

According to http://msdn.microsoft.com/en-us/library/ms188223.aspx:
To restore a database to a new location, you must edit the Restore As field for each file and specify a new destination path and/or filename. Changing the restore destinations in the Restore As column is equivalent to using the MOVE option in RESTORE statements.

So I guess I can use the GUI and things work as expected.  But the wording is a bit confusing to me... I was expecting the default value of the Restore As field to be the path used by the OLD server... and I thought I would have to manually change it here to affect the move.  But it seems to me that the restore database options default to storing the data files and log files to the proper path setup on the NEW server.

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question

Thanks for those reassurancesI
It looks like this is going to be easy-peasy.
I started with Experts Exchange in 2004 and it's been a mainstay of my professional computing life since. It helped me launch a career as a programmer / Oracle data analyst
William Peck