February 5, 2007 at 4:17 am
Has anyone come across any problems going from SQL Server 2000 SP3a to SQL Server 2005?
www.sqlAssociates.co.uk
February 5, 2007 at 5:28 am
what did you have in mind?
You can run in 2000 mode initially. The most likely issue you might have is with how the optimiser works ( it's slightly different ) which could make some less than optimal queries run badly. I've not found any problems.
Your biggest issue will be with any calls to system objects or tables, some third party products do some aweful stuff which will generally not work in 2005.
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
February 6, 2007 at 2:52 am
As far as doing te upgrade is concerned, I recommend uninstalling SQL 2000 and doing a clean install of SQL 2005.
You should script all your user objects from master, model, msdb in SQL 2000, and detach all user databases before doing the uninstall. In SQL 2005, script in your objects (after changing syntax where necessary) and attach the user databases. When you are happy everything is OK, set database compatibility to 'SQL 2005', set the other database options as appropriate, and rebuild all statistics.
If you do an in-place upgrade you end up with a mix of SQL 2000 and SQL 2005 folder locations and registry entries. I hae never got SAC to work after an in-place upgrade, and I would worry about other long-term support issues that may not apppear maybe for years. If you do a clean install of SQL 2005 then you know that everything should work, and anything that breaks is not caused by the upgrade process.
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 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply