If you were like us, and installed TFS 2010 as soon as it was released, then you’ve got it running on SQL 2008 as that was the latest version of SQL out at the time. Now the issue is that TFS 2012 doesn’t run on SQL 2008; it needs SQL 2008 R2 or SQL 2012.
|TFS 2010 supported editions of SQL Server||
Because we were intending on doing an in-place upgrade on the same hardware, we needed to get our TFS 2010 onto SQL 2008 R2 in preparation for this upgrade (We can’t go to SQL 2012, as TFS 2010 isn’t compatible with it).
So you’ll need…
- SQL 2008 R2 ISO (Same version, we’re using Enterprise)
- SQL Server® 2008 R2 Service Pack 1
- SQL Server® 2008 R2 Service Pack 2
You most certainly want to upgrade to SP2 asap because there’s an issue in SP1 that will leave your TFS Collection database corrupted (due to an issue with table compression).
If you are not defragmenting your TFS database(s) and re-indexing them you should do this before you perform this SQL upgrade as well as before the TFS upgrade itself.
The installation gotchya’s that I ran onto which are worth noting.
- After the SQL 2008 R2 installer installs the “setup support files’, it will say “Restart the computer is required”, but then setup will just continue on its merry way. YOU NEED TO REBOOT. Failure to cancelling the installation and actually doing a reboot here may leave you in this scenario.
- Note: For some people it is a little more complicated.
- During the installation i got “File in use” error, so I loaded up process explorer and sure enough, WMI was using the file. It’s safe to kill that process off, so issue seems to be documented here on the Microsoft Connect site.
- Our Reporting Services were set up to use HTTPS (For Web Service and Report Manger); the details for these bindings were lots during the upgrade so make sure that you know what they were, and check them afterwards.
Once the installation is complete you may want to do is run an update of the usage statistics
You’ll then need to reboot and install the two service packs.