Export (0) Print
Expand All

How to: Manually Install SQL Server 2008 for Team Foundation Server

If you install SQL Server 2008 for Visual Studio Team Foundation Server, you must install certain features, but other features are required only if you want to generate reports. SQL Server Express does not include Client Connectivity Tools, but you can add it by following the procedures in this topic.

NoteNote

For the best results, you should use the same edition of SQL Server for all servers that will host databases for a deployment of Team Foundation Server. For example, if you intend to use a separate server for reporting, you should ensure that it is running the same edition of SQL Server as the server that hosts the configuration database for Team Foundation Server.

NoteNote

If you are installing Team Foundation Server or SQL Server on Windows Server 2008 R2, you must have .NET Framework 3.5 installed. On Windows Server 2008 R2, you can install .NET Framework 3.5 by using the Add Features Wizard from Server Manager. For more information, see the following page on the Microsoft Web site: Adding Server Roles and Features

Requirements for Team Foundation Server

To run Team Foundation Server, you must install both the Database Engine and Full text search on the same instance of SQL Server. However, that instance does not have to run on the same server as Team Foundation Server.

Requirements for Reporting

If you want to generate reports that show data from Team Foundation, you must configure Team Foundation Server to use both SQL Server Analysis Services and SQL Server Reporting Services. You can install one or both of these features on the same server as Team Foundation Server, or you can install each feature on a different server from each other and from Team Foundation Server. 

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.

Team Foundation Server supports numerous SQL Server topologies, partly to accommodate teams with existing SQL Server installations. However, there are some guidelines for how to set up SQL Server for Team Foundation Server.

  • Single server: the Database Engine, Full text search, SQL Server Reporting Services, and Analysis Services on the same server that is running Team Foundation Server. If you do not want reporting, you do not need SQL Server Reporting Services, and Analysis Services. For more information, see Scenario: Installing Team Foundation Server on a Single-Server

  • Dual Server: SQL Server Reporting Services and Team Foundation Server running on the same server; the Database Engine, Full text search, SQL Server Analysis Services on another server. The scenario splits HTTP traffic from SQL Server traffic. If you do not want reporting, you do not need SQL Server Reporting Services, and Analysis Services.

  • Multiple Server: the Database Engine, Full text search on one server; SQL Server Reporting Services on a second server; Analysis Services on a third server (Reporting Services and Analysis Services could also be on the same server); and Client Tools Connectivity on the server that is running Team Foundation Server. If you do not want reporting, you do not need SQL Server Reporting Services, Analysis Services, or Client Tools Connectivity, effectively turning this into a dual-server topology.

For more information about deployments that use multiple server combinations, see Scenario: Installing Team Foundation Server Using Existing Infrastructure or More than One Server

Report Server

If you use reporting, Team Foundation Server requires a dedicated report server.

The report server requires its own relational database to function. This database is separate from the relational database that Team Foundation Server uses to provide reports. If you install SQL Server Reporting Services and the Database Engine on the same server, SQL Server setup can configure Reporting Services by setting up its required relational database on the Database Engine instance.

If you install Reporting Services without the Database Engine, you must manually configure Reporting Services after you install SQL Server. This involves specifying an instance of the Database Engine where you can host the relational database for the report server. For more information, see Configure Report Server Manually.

As a best practice for deployments of Team Foundation Server that use reporting, 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.

Required Permissions

To perform these procedures, you must be a member of the 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 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 2008

  1. Insert the installation DVD for SQL Server 2008 Enterprise Edition or Standard Edition, and double-click setup.exe.

    NoteNote

    The installation program for SQL Server offers to install the appropriate versions of the Microsoft .NET Framework and Windows Installer if they are not already installed. You must install these components to continue with the installation of SQL Server, and you must restart your server if you are prompted after these components are installed.

  2. On the SQL Server Installation Center page, click Installation, and then click New SQL Server stand-alone installation or add features to an existing installation.

  3. On the Setup Support Rules page, click OK.

  4. On the Product Key page, type your product key and click Next.

  5. On the License Terms page, review the license agreement. If you accept the terms and conditions, select the I accept the licensing terms check box, and then click Next.

  6. On the Setup Support Files page, click Install.

  7. On the Setup Support Rules page, click Next.

    NoteNote

    A Windows Firewall warning may appear, but this warning can be safely ignored. For more information about SQL Server ports required for Team Foundation Server, see Ports Required for Installation of Team Foundation Components.

  8. On the Feature Selection page, select the check boxes for the following components, and then click 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)

    • Client Tools Connectivity (required if no other SQL Server components are installed on the server that is running Team Foundation Server.)

    • Management Tools - Basic

    NoteNote

    To install Team Foundation Server, you do not need to install Management Tools (Basic or Complete) on the same computer as SQL Server. However, you must use SQL Server Management Studio to verify your installation of SQL Server.

  9. On the Instance Configuration page, click Default instance or Named instance. If you click Named instance, type the name of the instance. Click Next.

  10. On the Disk Space Requirements page, click Next.

  11. On the Server Configuration page, click Use the same account for all SQL Server services, or type the name of a domain account or NT AUTHORITY\NETWORK SERVICE in Account Name for every service.

    • If you specify a domain account, type its password in Password.

    • If you use NT AUTHORITY\NETWORK SERVICE, leave Password blank.

    • If you click Use the same account for all SQL Server services, you may still have to manually type account information for some services.

    In the Startup Type column, verify that Automatic appears for all services that you can edit, and then click Next.

  12. If you selected the check box for Database Engine Services in step 8, on the Database Engine Configuration page, click Windows authentication mode, click Add Current User, and then click Next.

    NoteNote

    You can set collation settings on this page and the next, Analysis Services Configuration. For more information, see SQL Server Collation Requirements for Team Foundation Server

  13. If you selected the check box for Analysis Services in step 8, on the Analysis Services Configuration page, click Add Current User, and then click Next.

  14. If you selected the check box for Reporting Services in step 8, on the Reporting Services Configuration page, click Install the native mode default configuration. If that option is unavailable, click Install, but do not configure the report server, and then click Next.

    If you plan to have the report server and Team Foundation Server on different servers and cannot automatically configure the report server, you must manually configure it after you finish installing SQL Server.

    NoteNote

    You should not click Install the SharePoint integrated mode default configuration. Team Foundation Server does not support this configuration mode.

  15. (Optional) On the Error and Usage Reporting page, select one or both check boxes to specify where information about errors and feature usage should be sent, and then click Next.

  16. On the Installation Rules page, click Next.

  17. On the Ready to Install page, review the list of components to be installed, and then click Install.

    The Installation Progress page shows the status of each component.

  18. After installation has completed, click Next.

  19. On the Complete page, click Close.

You must manually configure your report server if you could not configure Reporting Services when you installed SQL Server. If Reporting Services is on the same server as Team Foundation Server and you have not configured the report server, you are prompted during Team Foundation Server installation to complete the report server configuration, starting on step 3.

To manually configure a report server

  1. Click Start, point to All Programs, point to Microsoft SQL Server 2008, point to Configuration Tools, and click Reporting Services Configuration Manager.

    The Reporting Services Configuration Connection dialog box appears.

  2. 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.

  3. On the Reporting Services Configuration Manager page, click Start if the Report Service status reads Stopped.

  4. In the navigation bar, click Web Service URL.

  5. On the Web Service URL page, click Apply to accept the default values in the Virtual Directory, IP Address, and TCP Port boxes.

  6. In the navigation bar, click Database.

  7. On the Report Server Database page, click Change Database.

    The Report Server Database Configuration Wizard appears.

  8. On the Action page of the wizard, click Create a new report server database, and click Next.

  9. On the Database Server page of the wizard, type the name of a local or remote instance of SQL Server to host the database for the report server in Server Name, and click Next.

  10. On the Database page of the wizard, click Next to accept the default values in the Database Name, Language, and Native Mode boxes.

  11. In Credentials, click Next to accept the default values in the Authentication Type, User name, and Password boxes.

  12. On the Summary page of the wizard, verify your information, and click Next.

  13. On the Progress and Finish page of the wizard, click Finish.

  14. In the navigation bar for Reporting Services Configuration Manager, click Report Manager URL.

  15. On the Report Manager URL page, click Apply to accept the default value in the Virtual Directory box, and then click Exit.

You should configure the Windows service for Analysis Services to restart itself if it fails.

To configure Analysis Services to recover

  1. Click Start, point to All Programs, point to Administrative Tools, and then click Services.

  2. Right-click the Windows service for SQL Server Analysis Services (MSSQLSERVER), and then click Properties.

    If you are using a named instance of Analysis Services, the instance name appears in parenthesis.

  3. Click Recovery,

  4. In the First failure list, click Restart the Service.

  5. In the Second failure list, click Restart the Service.

  6. In the Subsequent failures list, click Restart the Service, and then click OK.

Community Additions

ADD
Show:
© 2014 Microsoft