CHAPTER 10 MANAGING REPORTS
database. You will need to have this database restored in order for the Pro_SSRS_Load_ExecutionLog
package and the reports created in this chapter to run. See the ReadMe.txt file for detailed instructions
on how to restore the Pro_SSRSExecutionLog database. You can download the Pro_SSRS project from
the Source Code/Download section of the Apress Web site (www.apress.com).
The Pro_SSRS_Load_ExecutionLog package is pretty straightforward. At the top of the package, we
just check for the existence of the database and if it does not exist, it branches to a statement that creates
the database, a table for archiving the Execution log and loads it with all records up to yesterday. If the
database already exists and the records are not already present in the database, then all of those records
are pulled into the archival database from the ReportServer database. Upon scheduling this package on
a nightly basis, it will get the data for the prior day. Figure 10-25 shows the package results after
completing a day’s load when run interactively in the development environment.Figure 10-25. Pro_SSRS_Load_ExecutionLog SSIS package Tip Note that the package needs to be executed regularly to keep the transformed log data current. In our
situation, we created a scheduled job for this purpose that runs the SSIS package every evening.Microsoft provides a set of sample reports that you can use with the ExecutionLog database. These
reports are included in the SQL Server 2008 installation in the following location: Samples\Reporting
Services\Report Samples\Server Management Sample Reports\Execution Log Sample Reports. The