September 30, 2009 at 6:57 am
I would also advise you detach all your user databases before you do the upgrade, and attach them after you are happy the upgrade is successful.
If your upgrade fails and your databases are attached, you cannot then re-attach them to a SQL 2000 instance.
I have seen situations where the SQL 2005 upgrade fails part way leaving SQL Server unable to start. If this happens you have to uninstall SQL and install a fresh copy. You need to prepare for this situation as part of your upgrade plan.
Personally, I would always install SQL 2005 on to a new server, then move the user databases across when the new instance is working OK.
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
September 30, 2009 at 7:39 am
If you do detach your databases make sure when you reattach you reset the owner of the database to what it was, and check the default database setting for logins is as it was before the detach
---------------------------------------------------------------------
September 30, 2009 at 9:21 am
Hi Edvassie,
Thanks a lot for your message. I really appreciate your help.
Thank You,
Best Regards,
SQLBuddy.
September 30, 2009 at 9:24 am
Hi George,
Thank you very much for your message. I really appreciate your help.
Best Regards,
SQLBuddy.
Viewing 4 posts - 16 through 18 (of 18 total)
You must be logged in to reply to this topic. Login to reply