To ensure that your installation of SQL Server will work with Team Foundation Server, you should verify that the required SQL Server features are available, the underlying Windows services that are associated with SQL Server are running, the connection settings are configured, and the network ports are open.
If SQL Server Reporting Services is not on the server that is running Team Foundation Server and you are using reporting, you must install Client Tools Connectivity on Team Foundation Server.
If the Database Engine, Analysis Services, and Reporting Services are running on different instances of SQL Server, you must log on to each server to verify each instance.
 Note |
|---|
If you are not using Team Foundation Server reporting, you do not need to verify SQL Server Reporting Services or Analysis Services. |
Required Permissions
To run SQL Server Configuration Manager, you must be a member of the Users security group on the server that hosts SQL Server. To use SQL Server Configuration Manager to modify services, you must be a member of the Administrators security group.
To run SQL Server Reporting Services Configuration Manager or SQL Server Management Studio, you must be a member of the Administrators security group on the operating system of the server that is running the instance of SQL Server that you want to verify. For SQL Server Management Studio, you must also be a member of the Public server role on the instance of SQL Server that you want to verify.
Verify Reporting Services
To verify that the Windows service is running using SQL Server Configuration Manager
On the server that is running SQL Server Reporting Services, click Start, point to All Programs, point to Microsoft SQL Server 2008, point to Configuration Tools, and then click SQL Server Configuration Manager.
Click SQL Server Services, and verify that Running appears in the State column for SQL Server Reporting Services.
To verify the report server URLs are running using SQL Server Reporting Services Configuration Manger
On the server that is running SQL Server Reporting Services, click Start, point to All Programs, point to Microsoft SQL Server 2008, point to Configuration Tools, and click Reporting Services Configuration Manager.
NoteOn Windows Server 2008, you must right-click Reporting Services Configuration Manager and click Run as administrator.
The Reporting Services Configuration Connection dialog box appears.
In Server Name, type the name of the report server. If you are using an instance name, type the name of the instance in Report Server Instance. Click Connect.
Click Report Manager URL, and click the link to the report manager website.
The report manager website for the report server opens in an Internet browser window.
Click Web Service URL, and click the link to the report server website.
The report server website opens in an Internet browser window.
| Note |
|---|
If SQL Server Reporting Services and Team Foundation Server are not on the same server, you must add the name of the service account that you will use for Team Foundation Server (TFSSERVICE) to the Content Manager group on the report server. This step is completed automatically during Team Foundation Server setup, if the report server is installed on Team Foundation Server. For more information, see Add the Service Account for Team Foundation Server to the Report Server |
Verify the Database Engine and Analysis Services
On the instance of SQL Server that is running the Database Engine, you must ensure that you have the Full-Text Search feature installed. To verify this functionality, you open the SQL Server Installation Center, and then click the New SQL Server stand-alone installation or add features to an existing installation. If Full-Text Search is not available on the instance of SQL Server that is running the Database Engine, you must install Full-Text Search. For more information about how to work with SQL Server Installation Center, see Manually Install SQL Server for Team Foundation Server.
To verify that Windows services are running by using SQL Server Configuration Manager
On the instance of SQL Server on which the Database Engine, SQL Server Analysis Services, or both are running, click Start, point to All Programs, point to Microsoft SQL Server 2008, point to Configuration Tools, and then click SQL Server Configuration Manager.
Click SQL Server Services, and verify that Running appears in the State column and the Start Mode is set to automatic for all services.
To change the start mode of a service to start automatically, right-click the service, click Properties, click the Service tab, click the drop-down list to the right of Start Mode, and then click Automatic.
To change a stopped service state to running, right-click the stopped service and click Start.
Click SQL Server Network Configuration, double-click Protocols for MyInstanceName, and verify that Enabled appears in the Status column for TCP/IP.
If you specified the default instance during installation, MyInstanceName will be MSSQLSERVER.
| Note |
|---|
As a best practice, you should configure the Windows service for Analysis Services to recover in case of failure. For more information, see "Configure Analysis Services to Recover on Failure" in Manually Install SQL Server for Team Foundation Server. |
To perform the following procedure, you must have SQL Server Management Studio installed. However, it does not have to be installed on the server that is running the instance of SQL Server that you are verifying. If you must install SQL Server Management Studio, see Manually Install SQL Server for Team Foundation Server.
To verify a connection to an instance of SQL Server by using SQL Server Management Studio
Click Start, point to All Programs, point to Microsoft SQL Server 2008, and then click SQL Server Management Studio.
The Connect to Server dialog box opens.
In the Server type list, click Database Engine or Analysis Services, depending on the type of installation that you are verifying.
Type the name of the server to which you want to connect, and then click Connect.
If SQL Server is installed on a cluster, you must specify the server name, not the computer name. If you are using a named instance of SQL Server, you must specify the name of the server and the name of the instance. If you cannot connect to the server, verify the firewall settings, and then try to connect again.
In Object Explorer, verify that a green arrow appears next to the server name.
See Also
