October 9, 2008 at 8:20 am
We are planning to move SQL Server 2005 32-bit to 64-bit. Our network engineer is doing the OS and then we were planning to reinstall SQL 2005 32-bit. Restore our master, model, and msdb databases. This way we keep all of our logins, legacy packages, linked servers, jobs, etc. Once that was done we were going to upgrade SQL to 64-bit.
Has anyone done this? Any issues I should know about?
Thanks,
Erin
October 9, 2008 at 9:05 am
I am not sure what you think you are gaining by installing the 32 bit version of SQL.
Have your ops guy install the 64 bit OS. Then you can just install the 64 bit SQL server, apply the service packs, and simply restore the backups you made while it was a 32 bit server. A 32 bit database backup can be restored on a 64 bit server - it works just fine.
The only major issue you may have is any SSIS packages that were created for the 32 bit environment. There are driver compatibility issues (for example no 64 bit Jet driver). None of this should impact the upgrade process, but you may have some packages that will not run on the 64 bit server. If you have to, you can still execute them using the 32 bit SSIS runtime that is installed with the 64 bit server install - it ends up in the 32 bit program files folder.
October 9, 2008 at 9:08 am
Can we restore master, model, msdb backups to a 64-bit when they were done from a 32-bit? Are such stored procedures as sys.sp_tables_info_90_rowset_64 on the 32-bit install?
October 9, 2008 at 9:35 am
http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=1519113&SiteID=1
Besides the Backup-and-Restore, Detach-and-Attach should work too (detach DB's in 32-bit, attach them in 64-bit)
I can't say for certain about system databases though, you should test it to be sure
Unless you can live with re-building everything. For my work, I just need to re-create all SQL Jobs, no big deal
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply