Tuesday, September 29, 2009 6:50 PMMy first upgrade from SQL Server 2008 RTM failed based on a Full Text Indexing option called "Import" which is the default for an upgrade. The error was "illegal characters in path". Next time through, (on a different instance) I changed that option to "Reset" which will reset the Full Text Indexes without rebuilding them. That did the trick. There is also a third option of "Rebuild" which will rebuild the Full Text Indexes with the new structure for R2. I was using a VM from the Microsoft Class 6235A for SSIS. Interestingly, there are no FT Indexes on the instance I was trying to upgrade from. Sounds like a CTP bug.
Subsequent upgrades to the same instance were not allowed as the upgrade process seems to think the instance has been already upgraded although it is clearly marked as 10.00.1600 and entirely usable for database access.
Wednesday, September 30, 2009 4:32 PM
Sorry to hear you are having troubles upgrading from RTM to R2. This forum addresses questions about the Application and Multi-Server Management aspects of SQL Server 2008 R2. It doesn't sound like the issue you describe is related to that feature.
A more appropriate forum is the setup and upgrade forum.
Also, you might consider filing the bug in connect.
All the best,
This posting is provided "as is" with no warranties, and confers no rights.
Wednesday, September 30, 2009 5:24 PMHi Brian,
In place upgrade is not supported in this CTP (August CTP).
In place upgrade will be supported in future CTPs.
While we tried to make this info widely available in the documentation (BOL and Release Notes),
I think it's normal for people not to realize it!
Sorry for the confusion.
Please test in-place upgrade when the next CTP comes out.