Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Can I migrate 32bit SQL Server 2005 database to 64bit SQL Server 2008 database without too much hassle or is there somethign I need to think about first?

share|improve this question
up vote 3 down vote accepted
  • When upgrading from a 64-bit edition of SQL Server to a 64-bit edition of SQL Server 2008, you must upgrade Analysis Services before you upgrade the Database Engine.
  • Back up all SQL Server database files from the instance to be upgraded, so that you can restore them, if it is required.
  • Run the appropriate Database Console Commands (DBCC) on databases to be upgraded to ensure that they are in a consistent state.
  • Estimate the disk space that is required to upgrade SQL Server components, in addition to user databases. For disk space that is required by SQL Server components, see Hardware and Software Requirements for Installing SQL Server 2008 R2.
  • Ensure that existing SQL Server system databases - master, model, msdb, and tempdb - are configured to autogrow, and ensure that they have sufficient hard disk space.
  • Ensure that all database servers have logon information in the master database. This is important for restoring a database, as system logon information resides in master.
  • Disable all startup stored procedures, as the upgrade process will stop and start services on the SQL Server instance being upgraded. Stored procedures processed at startup time might block the upgrade process.
  • Stop Replication and make sure that the replication log is empty.
  • Upgrading an instance of the SQL Server 2000 Database Engine retains the configuration value for max worker threads. However, we recommend that you change the max worker threads value to 0 before upgrading, to let the Database Engine calculate the optimal number of threads. For more information, see max worker threads Option in SQL Server Books Online.
  • Quit all applications, including all services that have SQL Server dependencies. Upgrade might fail if local applications are connected to the instance being upgraded.
  • If you utilize Database Mirroring, see How to: Minimize Downtime for Mirrored Databases When Upgrading Server Instances in SQL Server Books Online.
share|improve this answer
Much better answer :) – Ally Reilly Aug 12 '10 at 21:26

Not much to worry about really. You can either detach the db, move and reattach or backup and restore. Does the application that uses the db support 2008? If not then leave it in 90 compatability mode.

share|improve this answer
Data files/Backups do not vary with architecture – Ally Reilly Aug 12 '10 at 11:27

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.