Databases Reference
In-Depth Information
Server Configurations
There are two basic types of Reporting Services server configurations: Local Catalog and Remote
Catalog. The difference between them is where the Report Server database is located. A variation of the
remote catalog is distributed deployment. Since these are by far the most common types of Reporting
Services environments, let's take a closer look at them.
Local Catalog
This is the simplest configuration for a Reporting Services deployment. In this environment, the Reporting
Services databases are installed on the same server as Reporting Services. That is to say, SQL Server and IIS
are both running on the same box. Figure 11-5 shows a diagram of this type of deployment.
Report Server
Report Server Catalog
Report Manager
Internet Explorer
Report Builder Client
User Clients
IIS & SQL Server
Visual Studio 2005
Report Designer
Developers
SQL Server
Analysis Services
Other Source Databases
Source
Database
Figure 11-5
In this example, the source data — that is, the data displayed in the report — is on a separate machine
from the report server. The source data can be on SQL Server 2005 or any other data source that you can
connect with and get a result set returned to then work with in Reporting Services. The Report Server
instance and the Report Server Catalog live on the same server, which has both IIS and SQL Server
running on it. The client machines connect to the single report server to upload, view, and manage
reports. This type of deployment works best for light server loads.
Remote Catalog
In this configuration, the Report Server Catalog has been broken out onto its own machine. The Catalog,
you may recall, is comprised of both the ReportServer and ReportServerTempDB databases. Moving the
Report Server Catalog off of the machine hosting the report server instance greatly improves report
server performance. It can handle more client requests more quickly this way. Figure 11-6 shows an
example environment.
Search WWH ::
Custom Search