September 13, 2007 at 9:53 am
I've read of some people having problems using the "In-Place" upgrade path from 2000 to 2005. I have done it in a subset of my test environment without problems. We're using replication between servers and have some DTS packages. A developer here just mentioned that he thinks any OLEDB connection will have to be modified for 2005. I've run the Upgrade Advisor, which doesn't list any "show stoppers", although the OLEDB issue is not mentioned, I assume because it doesn't originate at the SQL Server.
What types of things have gone wrong ?? If it appears to upgrade successfully, are there some things I should look for that might be hidden problems ??
TIA
September 14, 2007 at 5:53 pm
I tested it (and couldn't find any issues), but still chose not to use the in place upgrade. I was just not comfortable with not being able to QUICKLY cut back to another system. So I did a side by side upgrade instead. Other than having to deal with an instance name, that was a good way to go.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply