November 5, 2013 at 7:38 am
I recently inherited a SQL 2012 32 bit installation running on a 64 bit OS. Has anyone ever performed such an in place upgrade? Is it even possible? I have a feeling I will be uninstalling and re-installing instead or performing an in place upgrade since the installation folder names are different between the two versions.
November 5, 2013 at 11:59 am
You cannot upgrade from 32-bit to 64-bit. It will be an uninstall/reinstall - unless you have a named instance or can use a named instance. In which case, you can create a new named instance and migrate the databases to the new instance.
You can make the uninstall/reinstall a bit easier...
First, make sure you have good backups of all databases. Also, script out the logins (sp_help_revlogin works well here), agent jobs and any custom objects in the master/msdb/model databases. If you have SSIS packages stored in MSDB - then export them to files or a BIDS project.
Validate the service account to be used for the install, validate you have the correct sa password. Verify all settings to be reset in case you have to rebuild the instance...
Once you have all of that done, shut down SQL Server (don't uninstall yet). Copy the system databases off to a secure location. Note where the system databases were installed...
Uninstall SQL Server, then reinstall - applying the same service packs and CU's (yes, has to be exactly the same here). Once that is completed, shut down SQL Server - copy the system databases to another secure location - and copy the system databases you saved off previously over the new system databases.
Restart SQL Server - it should come back up with the same databases attached, the logins, agent jobs, SSIS packages, etc...
good luck
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
November 5, 2013 at 1:30 pm
Thanks Jeffrey, I was pretty sure I was going to have to go down the uninstall, re-install path. So I guess I'll just handle it the same way I would when migrating to a new server by scripting out everything in advance and making backups of the databases and data files in advance.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply