Everything you want to know about Visual Studio ALM and Farming
Brian Harry is a Microsoft Technical Fellow working as the Product Unit Manager for Team Foundation Server. Learn more about Brian.
More videos »
With every release – of our product or a dependency, we think hard about the test/support matrix. As we developed Team Foundation Server 2012, we decided to support both SQL 2008 R2 and SQL 2012 – due to the close release proximity. TFS 2010, of course was released WAY before SQL 2012 and supported SQL 2008 and SQL 2008 R2.
When SQL 2012 was released we, not surprisingly, started getting requests for TFS 2010 to work with it. We thought it would likely “just work” and we just needed to run a test pass on it so we indicated, informally, that we expected to release support for it. As we got into the test pass, we found we were going to have to patch the TFS 2010 installer for some of the SQL 2012 changes – OK, we can do that. Then as we went even further, we found some work item tracking changes that needed to be made, realized that some of the best features of SQL 2012 (like AlwaysOn) wouldn’t be supported without significant work, etc.
Recently we’ve made the call to discontinue all efforts to get TFS 2010 working on SQL 2012. SQL 2012 is a great upgrade to SQL and to take advantage of it, you will need to upgrade your TFS to TFS 2012. TFS 2012 works great with SQL 2012 – including supporting cool new features like AlwaysOn.