July 14, 2009 at 4:39 pm
Hi all
currently I plan to upgrade my Cluster SQL Server 2000 to 2005 by using in-place method and my server is sensitive production and I have already another instance installed on the same cluster SQL server 2005 x64
my purpose is prepare a powerful rollback plan in case something happen during upgrade SQL 2000 Instance
please anyone have any suggestion or ideas please share it with me
Thanks, Regards
July 14, 2009 at 11:55 pm
Full proof plan for rolback MUST having upto date backup of all system as well as user database.
---------------------------------------------------
"Thare are only 10 types of people in the world:
Those who understand binary, and those who don't."
July 16, 2009 at 5:09 am
You will need to take disk images of all drives that contain program files that will be involved in the upgrade.
Some of the problems you encounter may leave you with SQL Server refusing to start. If this happens, take diagnostics and restore your disk images. You need to plan enough time in the upgrade process to allow for this rollback to be done. Remember that success is not guaranteed!
I also recomend detaching all your user databases before you start the upgrade. This means the user databases are isolated from any Windows or SQL Server related problems during the upgrade. You should prove that the cluster works after the upgrade has completed befoer re-attaching the user databases.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply