I am preparing an upgrade of an on-premises TFS 2010 instance to the cloud-based Azure DevOps Services, using Microsoft's Data Migration Tool for Azure DevOps Migration to facilitate the collection database move to Azure DevOps Services. There are however a few key points or caveats to highlight relating to this proposed upgrade and these are listed below.
- It will be an "In Place Upgrade", meaning we intend to use the existing "on-premises" hardware throughout the process.
- Our TFS 2010 instance is hosted on a Windows Server 2008 R2 Enterprise server.
- The Data Tier is implemented on a Microsoft SQL Server 2008 R2 instance.
Now, the Data Migration Guide recommends that to migrate to Azure DevOps Services, we first need to complete an upgrade from TFS 2010 to TFS 2013, as per the attached Upgrade path map. TFS 2013 however is not compatible with SQL Server 2008 R2 and requires SQL Server 2012 (Express, Standard, Enterprise).
On the other hand, TFS 2012 supports SQL Server 2008 R2 and can also then be upgraded directly to Azure DevOps Services, according to the Data Migration Tool's Recommended Upgrade Path. This, I believe will avoid the need to upgrade our current instance of SQL Server from SQL 2008 R2 to SQL Server 2012 (to upgrade to TFS 2013), in order to finally achieve our objective of upgrading to Azure DevOps Services.
Can anyone foresee any issues with this approach, or should we just bite the bullet and complete that SQL 2008 to SQL 2012 upgrade as suggested in the guide?