We recommend using Visual Studio 2017
This documentation is archived and is not being maintained.

Managing Data-Tier Servers for Team Foundation Server

The data tier for Team Foundation primarily consists of SQL Server databases and data stores, databases, and stored procedures. You can deploy the data tier with the application tier on a single physical server (single-server deployment), on a separate server (dual-server deployment), or across multiple servers. You can deploy the data tier across a SQL Server cluster. You can also deploy SQL Server Analysis Services on a separate physical server from the SQL Server databases.

The data-tier server hosts the following SQL Server databases, which Team Foundation Server requires:

  • ReportServer

  • ReportServerTempDB

  • STS_Config_TFS or WSS_Config

  • STS_Content_TFS or WSS_Content


    The names of the databases that contain data for SharePoint Products and Technologies will vary depending on the version of SharePoint Products and Technologies that is installed and whether the person who installed it customized the names. Additionally, if SharePoint Products and Technologies is installed on a separate server from Team Foundation Server, these databases might not reside on the data-tier server.

  • TfsBuild

  • TfsIntegration

  • TFSWarehouse

  • TfsVersionControl

  • TfsWorkItemTracking

  • TfsWorkItemTrackingAttachments

  • TFSActivityLogging

For a description of each database, see How to: Back Up Team Foundation Server.

These databases require the following services:


  • SQL Server Agent (TFSINSTANCE)

  • SQL Server Analysis Services (TFSINSTANCE)

  • SQL Server Browser

In addition to its own services, Team Foundation Server requires several other services to operate. For more information about required services for the data-tier server, see Team Foundation Server Security Concepts.

The data-tier server also hosts the applications that it requires to operate with the application-tier and client-tier servers. For more information, see Team Foundation Server Security Architecture.

The size and scope of your deployment of Team Foundation Server affect the hardware and software that you need for the server or servers that host the data tier. For more information, see Requirements for Team Foundation Components and Application-Tier Server Requirements for Team Foundation.

How to: Rename a Data-Tier Server

Describes how to rename the server on which the data tier resides, including redirecting Reporting Services, stopping and restarting services, and refreshing the cache on client computers.

How to: Uninstall a Data-Tier Server

Describes the process of uninstalling a data-tier server and provides a link to the installation guide and information about what is and is not removed from the system.

How to: Verify Team Foundation Server Fail-Over in a Cluster

Describes how to inspect the status of the Team Foundation services on the application tier and verify that the cluster and the generic script resource work if the active node is taken offline.

How to: Move the Analysis Services Database to a Separate Server

Describes how to move the data warehouse so that the logical data tier will comprise two servers: one server that hosts the relational databases and one server that hosts the database for SQL Server Analysis Services.

How to: Work with SQL Server Named Instances

Describes how to use named instances of SQL Server with Team Foundation Server and provides a brief overview of the prerequisites and requirements for that approach.