Enterprise Deployment Model
This topic describes the deployment model that you can implement to support a large installation. It also includes a brief section about configuring a report server for Internet access.
Clustering Support in Reporting Services
Reporting Services supports clustering so that you can create a highly available and scalable report server installation. A report server Web farm consists of multiple report servers that share a single report server database (or a cluster of report server databases). You must use additional software to configure and manage the cluster. You can cluster report servers, report server databases, or both.
A report server database can be part of a SQL Server failover cluster. After you install Reporting Services, you can use features in SQL Server 2000 to create a cluster based on the existing report server database. Whether you use a single database or a database cluster, the configuration you use is transparent to a report server.
The following diagram shows multiple report servers and report server databases deployed in separate clusters.
All report servers must be Enterprise Edition, Developer Edition, or Evaluation Edition. Standard Edition does not support the Web farm feature.
You must also have third-party software that provides clustering functionality. Microsoft recommends the use of Microsoft Application Center or third-party software to create and maintain a report server Web farm. You can also use Windows server features to create a Network Load Balancing (NLB) cluster.
Steps for Deploying a Report Server Web Farm
The following steps are necessary for deploying two or more report servers in a Web farm.
- Run Setup to install a report server instance and create a report server database. The report server database can be local or on a remote SQL Server instance.
Important Report server and the SQL Server instance hosting the report server database must be in the same domain or in a trusted domain.
- Run Setup again on a second computer to install a second report server. Specify the report server database that you created in step 1. You can choose any combination of features except the Adventure Works sample database (the database may already be installed; furthermore, you can only install the sample database on a local SQL Server). For more information, see Installing a Report Server Web Farm.
- Repeat step 2 until you have installed all of the report servers that will be part of the Web farm.
- Install and configure Web farm software that provides clustering and load balancing functionality. Microsoft recommends the use of Microsoft Application Center or third-party software to create and maintain a report server Web farm. You can also use Windows server features to create a Network Load Balancing (NLB) cluster.
Deploying a Report Server NLB Cluster
If you know how to implement and maintain NLB clusters, you can deploy a report server Web farm using the functionality available in a Microsoft Windows server-based operating system.
At the time that this documentation was written, Reporting Services has been tested on an NLB cluster that includes an Active Directory domain controller, three report servers, a dedicated computer hosting a SQL Server instance for the report server database, and a large number of client computers running a variety of operating systems. In addition to the main network connection, the report servers were connected to a hub through secondary network cards. Windows product documentation recommends the use of a second network card to offload network traffic generated by the NLB nodes.
After you have installed Reporting Services software (steps 1 through 3 noted in the previous topic), choose one of the report servers as the first NLB node. You can use the default values to configure the node. After the first node is configured, you can join additional nodes to the cluster.
Deploying a Report Server for Internet Access
Settings in the rswebapplication.config file provide values that are used to direct requests from Report Manager to a report server. By default, the configuration file includes ReportServerUrl. Report Manager uses this value to find the report server that contains server state information and stored items. In an intranet deployment model, the Report Manager connects to a report server using a network name (for example, http://server01/reportserver).
To access a report server on the Internet, you must add a ReportServerExternalURL configuration setting that specifies the fully qualified domain name of the report server. The external client uses this value to access a report server. In this scenario, the browser that is hosting Report Manager must send a fully qualified domain name when making requests on behalf of Report Manager to the report server.
The following example illustrates the syntax for ReportServerExternalURL: