In this post, we’re going to install all the SQL Server 2012 features that TFS requires on the same server as TFS, but this isn’t a requirement. TFS is very flexible with regard to SQL Server topologies. See One Server or Two?
TIP: You can also use an existing installation of SQL Server for TFS, but to do this you’ll need the SQL Server administrator to grant you a lot of privilege. You must be a member of the sysadmin Server role in SQL Server to install and configure TFS. Why does TFS need so much privilege on the SQL Server? (Brian Harry blog post)
One Server or Two?
If you’re only going to use one server for TFS, you can safely ignore this section.
If you plan to have more than 500 users accessing your TFS server, the recommendation is to put SQL Server on a second server. This splits the load between TFS and its configuration database. You could install all the SQL Server features TFS requires on that second server, or you could split the features up. Some teams like to put the report server on the TFS server, and the Database engine, Full text search, and Analysis services on the second server, splitting HTTP traffic from SQL Server traffic.
There are many different topology choices you could make. In general, TFS allows you to install SQL Server instance features (Database engine, Reporting Services, Analysis Services) on different servers. Here are some caveats for various SQL Server topologies to keep in mind:
- TFS requires the Database Engine and Full text search features on the same instance.
- TFS reporting is optional, but if you want reporting you must install Reporting Services and Analysis Services (each can go on its own server, if you want that topology). If you skip reporting, you don’t have to setup Reporting Services or Analysis Services.
- If you don’t install any SQL Server instances on the TFS server, you must at least install the SQL Server feature Client Tools Connectivity on TFS. If you have a SQL Server instance on the TFS server (either the Database Engine, Reporting Services or Analysis Services) you don’t have to install Client Tools Connectivity.
If you want to install SQL Server features on different servers, run the SQL Server installation on each server where you want to install a feature. Use the same instructions below for each installation, but at step 9, only install the features that you require.
TIP: A multiple-server installation of TFS requires an Active Directory domain and domain accounts or the Network Service account. You cannot use local accounts for service accounts.
To perform these procedures, you must be a member of the Windows Administrators security group on the server on which you are installing SQL Server.
To manually configure a report server, you must also be a member of the Windows Administrators security group on the SQL Server that hosts the report server database, if this instance of SQL Server is not on your report server.
To install SQL Server for TFS
1) Insert the installation DVD for a supported version of SQL Server and launch setup.exe.
You can find more detailed information about SQL Server Requirements for Team Foundation Server on MSDN, but this instruction will guide you through most installations.
2) On the SQL Server Installation Center page, choose Installation, and then choose New installation or add features to an existing installation.
3) On the Setup Support Rules page, choose OK.
4) On the Product Key page, type your product key or specify a free edition and then choose Next.
5) On the License Terms page, accept the license agreement and choose Next.
6) On the Setup Support Files page, choose Install (SQL Server 2008 R2 only).
7) On the Setup Support Rules page, choose Next.
TIP: A Windows Firewall warning might appear, but you can safely ignore this warning if you’re planning to install TFS on the same server. TFS automatically adds an exception to Windows Firewall for SQL Server. If you’re installing TFS on some other server, you’ll want to open a port for SQL Server in Windows Firewall on this server. For more information about SQL Server ports required for Team Foundation Server, see Ports Required for Installation of Team Foundation Server.
8) On the Setup Role page, choose SQL Server Feature Installation and then choose Next.
9) On the Feature Selection page, select the check boxes for one or more of the following components, depending on the topology you intend to use, and then choose Next:
- Database Engine Services (required for Team Foundation Server)
- Full-Text and Semantic Extractions for Search or Full-Text Search ¹ (required for Team Foundation Server)
- Analysis Services (required for reporting)
- Reporting Services – Native or Reporting Services ¹ (required for reporting)
- Client Tools Connectivity (required if no other SQL Server components are installed on the server that is running Team Foundation Server.)
- Management Tools – Basic ²
10) On the Installation Rules page, choose Next.
11) On the Instance Configuration page, choose Default instance. If you choose Named instance, type the name of the instance. Choose Next.
12) On the Disk Space Requirements page, choose Next.
13) On the Server Configuration page, do one of the following:
For SQL Server 2012, you can accept the defaults or enter the name of a domain account or NT AUTHORITY\NETWORK SERVICE in Account Name for every service.
For SQL Server 2008 R2, choose Use the same account for all SQL Server services,³ or enter the name of a domain account or NT AUTHORITY\NETWORK SERVICE in Account Name for every service.
No matter which version of SQL Server you use, if you specify a domain account, type its password in Password. If you use NT AUTHORITY\NETWORK SERVICE, leave Password blank.
14) In the Startup Type column, verify that Automatic appears for all services that you can edit, and then click Next.
NOTE: You can set collation settings on this page. For more information, see SQL Server Collation Requirements for Team Foundation Server.
15) If you selected the Database Engine Services check box in step 9, on the Database Engine Configuration page, choose Windows authentication mode, choose Add Current User, and then choose Next. Otherwise skip to the next step.
16) If you selected the Analysis Services check box in step 9, on the Analysis Services Configuration page, choose Add Current User, and then choose Next. Otherwise skip to the next step.
17) If you selected the Reporting Services check box in step 9, on the Reporting Services Configuration page, choose Install and configure (SQL Server 2012) or Install the native mode default configuration (SQL Server 2008 R2). If those options are unavailable, choose Install only (SQL Server 2012) or Install, but do not configure the report server (SQL Server 2008 R2) and then choose Next.
If you had to choose Install only or Install but do not configure the report server, you may be planning to have the report server and Team Foundation Server on different servers. This is a supported topology, but you will have to manually configure the report server after you finish installing SQL Server. Use these instructions: Configure Report Server Manually
NOTE: You should not click Reporting Service SharePoint Integrated Mode (SQL Server 2012)or Install the SharePoint integrated mode default configuration. Team Foundation Server does not support this configuration mode.
18) (Optional) On the Error and Usage Reporting page, specify whether to send information about errors and then choose Next.
19) On the Installation Configuration Rules page, choose Next.
20) On the Ready to Install page, review the list of components to be installed, and then choose Install.
The Installation Progress page shows the status of each component.
21) On the Complete page, choose Close.
¹ In SQL Server 2008 R2, feature names are slightly different than those in SQL Server 2012. This procedure lists feature names from both versions, but you only need to install the feature appropriate for the version of SQL Server you are installing.
² To install Team Foundation Server, you do not need to install Management Tools (Basic or Complete) on the same computer as SQL Server or TFS. However, you will need the SQL Server Management Studio management tool to manage your installation of SQL Server.
³ If you click Use the same account for all SQL Server services (SQL Server 2008 R2 only), you may still have to manually enter account information for some services.