asked
Upgrade 2005 to 2008
Can anyone tell me the potential/frequent issues noticed during upgrade from sql 2005 to 2008 version. What are the solutions and preventive measures? Rgds Aj -------- Matt, Can you please advise,what do you mean by "Make sure your backups are usable first",unabl to add comments via "Add new comment" button,hence posted my comments here. --- Matt,thank you for asking, When I click on "Add new comment" button there is no change in the screen,nither I see the comment box where I can input my comments.I am not sure how can I update my comments? Rgds, Ajit
Ajit - what do you mean about add new comment? Can you describe a bit more about what it says? Because I tested this last week and it was OK - so maybe I'm doing something different?
Ajit - Ok thanks - one final question - can you let me know what O/S and Browser you are using? Thanks again
2005 to 2008 is generally a pretty smooth upgrade, but it's worth taking all usual precautions: * Make sure your backups are usable first * Upgrade side-by-side if possible, rather than in-place * Make sure all statistics are updated, ideally take the opportunity to reindex all indices beforehand * Make sure you have a backout plan if it all goes pear shaped [This question][1] also has a couple of useful links. [1]:
http://ask.sqlservercentral.com/questions/86/upgrading-to-sql-server-2008-from-sql-server-2005
By "Make sure your backups are usable first", I assume you mean "make sure you can restore from the backup to a new similar server"... (Clarifying for Ajit...)
There are a few T-SQL commands that have become deprecated in 2008. One of the big ones is BACKUP LOG WITH NOLOG and BACKUP LOG WITH TRUNCATEONLY no longer works. You can trace for [Deprecation Final Support Event][1] in Profiler which will let you know if your using any commands that will not work in 2008. It's also a very good idea to run the [Upgrade Advisor][2] and review the output. [1]:
http://msdn.microsoft.com/en-us/library/ms178053%28SQL.90%29.aspx [2]:
http://www.microsoft.com/downloads/details.aspx?FamilyID=f5a6c5e9-4cd9-4e42-a21c-7291e7f0f852&displaylang=en
Personally, I would always go for upgrading to new hardware / vm. That way, you've got no problems with going back to the previous version. * Check your backups anyway * Check the database structures (DBCC CheckDB) * Matt suggests rebuilding index stats - I would leave that until it's on the new box, assuming that the new box is a more powerful server... * Detach the database * Copy the database & log files to the new server * Reattach on the old server * Attach on the new server * Side-by-side testing Backout plan? Well, you've not destroyed anything... I've prepared a [little list of other things to look at when migrating / upgrading][1] on my blog. If you can spot anything missing, let me know! [1]:
http://thelonedba.wordpress.com/2010/06/08/sql-server-upgrades-ahoy/
