Reporting Services Architecture - Professional SQL Server 2005 Reporting Services - page 63

Table Name Function

Event Temporary storage location for event notification. Populated by SQL

Server Agent and then executed by the Reporting Services Windows
service.

ActiveSubscriptions Subscription success/failure information.

RunningJobs Currently executing scheduled processes.

Administrative

Configuration Reporting Services configuration settings. These should only be

administered using the Reporting Services configuration utilities.

Keys Listing of public and private keys for data encryption.

ExecutionLog List of reports that have been executed, when they started execution,

when they finished execution, the user making the request, and the
parameters used.

Report Models

ModelDrill Contains information used when implementing Report Builder infi-

nite drill-down feature. Lists reports and their associated report
model.

ModelItemPolicy Association among a given report item, model, and policy.

ModelPerspective Association between a given report model and its perspectives.

When working with Reporting Services, it is important to pay close attention to the
ReportServer database. It contains all critical information related to Reporting
Services and should be backed up on a regular schedule.

ReportServerTempDB
As the name implies, the ReportServerTempDB database stores temporary Reporting Services informa-
tion. User session information is stored in the ReportServerTempDB. Because Reporting Services com-
municates using HTTP, no state is maintained between the client application and server. Session state
about the reports that the user is running must be stored between each server call. The
ReportServerTempDB stores this information in a SessionData table.

ReportServerTempDB also stores report cache information. When a report is set as a cached instance,
there is no definite time when that report is executed. It depends on which process requests the report
first. Once the report is executed, the intermediate format and data are stored in the ReportServer
TempDB database. If this database were to fail, the cached information would be lost. But, since it is
executed when a user views the report, there is no real loss of information. Snapshots, on the other hand,
are not stored here. Their execution time is usually at a set moment to ensure that the data on the report
is correct. Therefore, this information is stored in the more permanent ReportServer database.