How to set up SQL Server
First you install and configure SQL Server 2008 R2 for Team Foundation Server with reporting. If you’re using SQL Server 2008 R2 Enterprise edition, you have to update to cumulative update package 1 for SQL Server 2008 R2 Service Pack 1 (or a later version) to address a SQL Server issue with table compression.
After you complete the install, you configure Windows Server to recover analysis services on failure.
Tip: Make sure the default collation settings in SQL Server match the existing settings from the SQL Server instance that you’re migrating from. There’s more information about this on MSDN: SQL Server Collation Requirements for Team Foundation Server
To perform these procedures, you must be a member of the Administrators security group on Windows Server.
To install Database Engine, Analysis Services and Reporting Services
- Launch setup.exe on the SQL Server DVD.
- On the SQL Server Installation Center page, choose Installation, and then choose New installation or add features to an existing installation.
- On the Setup Support Rules page, choose OK.
- On the Product Key page, type your product key or specify a free edition and then choose Next.
- On the License Terms page, accept the license agreement and choose Next.
- On the Setup Support Files page, choose Install.
- On the Setup Support Rules page, choose Next.
Tip: A Windows Firewall warning might appear here, but you can safely ignore this warning. TFS automatically adds an exception for Windows Firewall during upgrade.
- On the Setup Role page, choose SQL Server Feature Installation and then choose Next.
- On the Feature Selection page, select the check boxes for the following components and then choose Next:
- Database Engine Services (required for Team Foundation Server)
- Full-Text Search (required for Team Foundation Server)
- Analysis Services (required for reporting)
- Reporting Services (required for reporting)
- Management Tools – Basic (Management Tools -Complete automatically selects itself when you click Basic and this is fine)
- On the Installation Rules page, choose Next.
- On the Instance Configuration page, choose Default instance. If you choose Named instance, type the name of the instance. Choose Next.
- On the Disk Space Requirements page, choose Next.
- On the Server Configuration page, choose Use the same account for all SQL Server services, and enter NT AUTHORITY\NETWORK SERVICE in Account Name for every service.
- If you do specify a domain account, enter its password in Password.
- If you use NT AUTHORITY\NETWORK SERVICE, leave Password blank.
- If you choose Use the same account for all SQL Server services, you might still have to manually enter account information for some services.
- In the Startup Type column, verify that Automatic appears for all services that you can edit, and then choose Next.
- On the Database Engine Configuration page, choose Windows authentication mode, choose Add Current User, and then choose Next.
- On the Analysis Services Configuration page, choose Add Current User, and then choose Next.
- On the Reporting Services Configuration page, choose Install the native mode default configuration, and then choose Next.
- (Optional) On the Error and Usage Reporting page, specify whether to send information about errors and then choose Next.
- On the Installation Rules page, choose Next.
- 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.
- On the Complete page, choose Close.
Update SQL Server 2008 R2 Enterprise edition
If you’re using SQL Server 2008 R2 Enterprise edition, you have to update to cumulative update package 1 for SQL Server 2008 R2 Service Pack 1 (or a later version) to address a SQL Server issue with table compression. If you’re using SQL Server 2008 R2 Standard edition or SQL Server 2012, you don’t have to update SQL Server.
Configure Analysis Services to recover on failure
You should configure the Windows service for Analysis Services to restart itself if it fails.
To configure Analysis Services to recover
- Open the Services control panel (Start >Administrative tools >Services).
- Right-click the Windows service for SQL Server Analysis Services (MSSQLSERVER), and then choose Properties. If you are using a named instance of Analysis Services, the instance name appears in parenthesis.
- Choose Recovery.
- In the First failure list, choose Restart the Service.
- In the Second failure list, choose Restart the Service.
- In the Subsequent failures list, choose Restart the Service, and then choose OK.
Next Step: Set up SharePoint
If you don’t skip the portal setup, you have two options for how to deal with SharePoint:
- Use the same SharePoint site you have right now.
If your old SharePoint server is still up and running, you can continue to use it. Go to the SharePoint server and uninstall old extensions, and then install the new extensions before you upgrade TFS. If SharePoint and the previous verison of TFS were on the same computer, you have to uninstall the entire TFS 2010 application tier. In the new upgraded configuration, the only TFS component on the SharePoint server will be the TFS extensions for SharePoint.
When you upgrade TFS, the upgrade wizard will recognize and configure your remote SharePoint site to work with all the projects and collections on the new upgraded TFS server. Make sure the account you’re going to use as the service account for TFS is a member of the Farm administrators group on SharePoint.
For more information: Use the same SharePoint site that you have right now
- Move SharePoint to a new server. This is a little more complicated.For more information: Move SharePoint to New Hardware for TFS
If you don’t want SharePoint in your deployment, run the TFS upgrade wizard instead.