Execution Properties Page (Report Manager)

Use the Execution properties page to set report execution properties for the currently selected report. These options determine when report processing occurs. You can set these options to run a report during off-peak hours. If you have a report that is accessed frequently, you can temporarily cache copies of it to eliminate wait time if multiple users are accessing the same report within minutes of each other.

Use this option when you want the report to run when the user selects the report. If a cached copy of the report is available, it is returned to the user; otherwise, data retrieval and rendering occurs when a user selects the report.

Choose Do not cache temporary copies of this report to always run the report with the most recent data. Each user who opens the report triggers a query against the data source that contains data used in the report.

Choose Cache a temporary copy of the reportto place a temporary copy of the report in a cache when the first user opens the report. Performance is faster for subsequent users who open the report because the report is returned from the cache instead of being processed again.

Cached reports must expire after some length of time. You can type the number of minutes after which the temporary copy of the report is no longer valid. Once a temporary copy is invalidated, it is no longer returned from cache. The next time a user opens the report, the report server processes the report again and places a copy of the refreshed report back in the cache.

You can also use a schedule to expire a cached report using a frequency other than minutes. For example, to expire a cached report at the end of the day, you can pick a specific hour at night after which the copy expires.

Render this report from a report execution snapshot

Use this option to process this report as a snapshot, at a time that you schedule. Choose this option when you want a report to run during off-peak hours. Unlike cached copies that are created when a user opens the report, a snapshot is created and subsequently refreshed on a schedule. Snapshots do not expire; they remain in service until they are replaced by newer versions.

Snapshots that are generated as a result of report execution settings have the same characteristics as report history snapshots. The difference is that there is only one report execution snapshot and potentially many report history snapshots. Report history snapshots are accessed from the History page of the report, which stores many instances of a report, as it existed at different points in time. In contrast, users access report execution snapshots from folders the same way that they access live reports. In the case of report execution snapshots, no visual cue exists to indicate to users that the report is a snapshot.

Create a snapshot of the report when you click Apply on this page

Use this option to create a report snapshot when you click Apply. When you process a report as a snapshot, you can generate it right away to make it available before the scheduled start time.

Report Execution Timeout

Specify whether report processing times out after a certain number of seconds. If you choose the default setting, the timeout setting that is specified in the Site Settings page is used for this report.

This value applies to report processing on a report server. It does not affect data processing on the database server that provides the data for your report.

The count for report processing begins when the report is selected and ends when the report opens. When you set this value, specify enough time to complete both data processing and report processing.