June 8, 2007 at 10:48 am
We probably do an in-place upgrade of our current 2-node cluster from 200 to 2005. There are 7 instances with not very large databases. Also to this cluster we have to add some stand-alone instances/databases. There are very few DTS packages, I am not worried about these. Apart from having a strong roll-back plan, any ideas/suggestions for known/unknown issues. Current SQL instances have SP4.
Thanks,
June 11, 2007 at 5:34 am
You should only consider a in-place upgrade from SQL 2000 to SQL 2005 if all other options are impossible.
The result of an in-place upgrade is messy. You have a mixture of SQL 2000 and SQL 2005 registry keys and file locations. Some of the SQL 2005 tools do not work (they appear to assume a file path containing MSSQL.n where n is numeric, but this does not exist with an in-place upgrade.)
The in-place upgrade is very brittle if you have changed the location of your system databases. In some tests I did the upgrade worked, but in others SQL was broken and I had to uninstall and re-install to get it to work (The SQL 2000 configuration was supposed to be identical for both these tests...!).
The SQL 2005 SP2 install puts new versions of mssqlsystemresource (and distmdl if you use this) in the default location, and expects to use them when it restarts SQL. Again, in the worst case I had to re-install SQL 2005 to overcome this.
You should never assume with any in-place upgrade to SQL 2005 that it will work for a given SQL 2000 instance, and even if the RTM instal works you may hit issues later with SP or Hotfix rollup installs.
If you want to take these risks, then go ahead with an in-place upgrade, but get your manager to sign-off that the risks are acceptable to the business.
The alternative is to uninstall SQL 2000, then install SQL 2005, which has always worked for me. On a Production server, I would only want to install SQL 2005 to a new server, keeping the SQL 2000 server available until for a few days after SQL 2005 goes live.
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
June 11, 2007 at 6:51 am
Looks like this is route we will take. We will upgrade all the instances and not have a mix of 2000 and 2005 as these are clustered instances. Applications that are not 2005 complaint will have their databases running in 2000 compatible mode.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply