Can anyone tell me the potential/frequent issues noticed during upgrade from sql 2005 to 2008 version.
What are the solutions and preventive measures?
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?
2005 to 2008 is generally a pretty smooth upgrade, but it's worth taking all usual precautions:
This question also has a couple of useful links.
answered Jul 27, 2010 at 12:28 AM
Matt Whitfield ♦♦
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 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 and review the output.
answered Jul 27, 2010 at 12:34 AM
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.
Backout plan? Well, you've not destroyed anything...
I've prepared a little list of other things to look at when migrating / upgrading on my blog. If you can spot anything missing, let me know!
answered Jul 27, 2010 at 02:13 AM