Querying and Reporting on Report Execution Log Data

Reporting Services stores execution data across several tables in the report server database. Because the internal table structure does not present report execution log data in a format that is accessible to users, you should extract the log data and store it in a separate local report execution log database.

Extracting Execution Log Data

To make data extraction easier, Reporting Services includes a sample SQL Server Information Services package called RSExecutionLog_Update.dtsx. The package extracts the data from the report execution log and puts it into a table structure that you can query. A sample database script file is provided that creates the table structure used by the package. The following files are used to create the database and extract data:

  • RSExecutionLog_Update.dtsx
  • RSExecutionLog_Update.dtsConfig
  • Createtables.sql

Reporting on Execution Log Data

Samples reports are also included that retrieve report execution data from the local report execution log database. The reports work with a local database that contains execution log data. Once you create the database, you can run the package to fill it with data, and then run the reports to view information about report activity.

The following sample reports provide information about report server activity:

  • Execution Status Codes.rdl
  • Report Summary.rdl
  • Execution Summary.rdl

Sample package, script, and report files are installed as SQL Server samples. For more information about how to install the samples and deploy packages and reports, see Installing AdventureWorks Sample Databases and Samples and Server Management Report Samples.

Refreshing Execution Log Data

To refresh the report execution log database with more recent data, run the RSExecutionLog_Update.dtsx package periodically. The package appends new log entries to the existing entries. It does not remove old entries or historical data. Examples of historical data might include users who no longer run reports on a report server, computer names that are no longer in service, or reports that no longer exist. If you do not want to save historical execution log data, you can periodically run the Cleanup.sql query on the report execution log database.

  1. In SQL Server Management Studio, select RSExecutionLog from the Available Databases list box on the tool bar.
  2. Click File, point to Open, and then click File. By default, the file is located at \90\Samples\Reporting Services\Report Samples\Report Execution Log Sample Reports\Cleanup.sql. Select that file, and then click OK.
  3. Click Execute on the tool bar to run the query.

See Also


Reporting Services Log Files

Other Resources

Reporting Services Errors and Events

Help and Information

Getting SQL Server 2005 Assistance