SQL Server Requirements for Team Foundation Server
Team Foundation Server requires SQL Server 2008 R2 or SQL Server 2012. You have multiple SQL Server options:
You can use the basic configuration of Team Foundation Server, which comes with SQL Server 2012 Express.
You can install one of the supported editions of SQL Server 2008 or SQL Server 2012.
You can use an existing installation of SQL Server 2008 or SQL Server 2012.
Regardless of which option you choose, your instance of SQL Server must meet the following requirements:
Required for Team Foundation Server
Required for reporting
For more information, see SQL Server Collation Requirements for Team Foundation Server.
You can use a domain account or a built-in account.
¹ Limited or no SQL Server High Availability support.
² If you’re using SQL Server 2008, R2 Enterprise Edition you need to update to cumulative update package 1 for SQL Server 2008 R2 Service Pack 1 to address a SQL Server issue with table compression.
SQL Server 2012 brings with it a new high availability (HA) feature that requires a Team Foundation Server-specific configuration, and new recommendations for which HA features to use. In Team Foundation Server 2010, a lot of work went into making Team Foundation Server independent of the SQL Server configuration, especially regarding its HA features. The goal was that Team Foundation Server would work without any HA-specific configurations, no matter which HA feature you used. The reality is that the breadth of HA features in SQL Server is too great to pledge support for all of them, and Always On Availability Groups does require a small amount of TFS specific configuration.
SQL Server HA feature
Requires TFS Configuration
Always On Failover Cluster Instances¹/ Failover Clustering
Always On Availability Groups²
For more information, see: Use SQL Server 2012 Always On Availability Groups with Team Foundation Server
SQL Log Shipping
¹ Always On Failover Cluster Instances was known as “Failover Clustering” in versions before SQL Server 2012.
² Available only in SQL Server 2012.
³ Deprecated feature. Available only in SQL Server 2008 R2.