Databases Reference
In-Depth Information
Report Server
Report Manager
Internet Explorer
Report Builder Client
User Clients
IIS & SQL Server
Visual Studio 2005
Report Designer
Developers
Report
Server
Catalog
Source
Database
SQL Server
ReportServerDB
ReportServerTempDB
SQL Server
Analysis Services
Other Source Databases
Figure 11-6
Just moving the Report Server Catalog off the machine that has Reporting Services installed will net you
a noticeable increase in performance. The Report Server Catalog and the source database can be on the
same database server, separate from the machine that IIS is running on.
Web Farm Deployment
Reporting Services is an ASP.NET web-based application. For a long time, customers have been scaling
such web-based applications using scale-out. A few reasons scale-out has proven to be popular is that it:
❑
Enables customers to incrementally add (or remove) capacity as needed.
❑
Offers a very affordable, manageable, and flexible way to add/remove that capacity.
❑
Allows heavy workloads to be balanced across multiple commodity servers.
❑
Inherently offers a certain degree of fault tolerance.
Customer input drives the features and capabilities that Microsoft designs into products and Reporting
Services is no exception. Reporting Services was built with the knowledge that most people would
decide to deploy it across a multiple servers. As a result, Reporting Services scales very well in a web
farm configuration. Deploying Reporting Services to an environment that includes clustered IIS and SQL
Servers allows your report servers to handle all but the most extreme request load. Figure 11-7 shows an
example configuration.
Search WWH ::
Custom Search