Set Report Processing Properties
Topic Status: Some information in this topic is preview and subject to change in future releases. Preview information describes new features or changes to existing features in Microsoft SQL Server 2016 Community Technology Preview 2 (CTP2).
Report execution properties control how a report is processed. Execution properties must be set for each report individually.
To set report execution properties, open the report in Report Manager, and then navigate to the Execution properties page. For more information, see Processing Options Properties Page (Report Manager). You can also set properties using SQL Server Management Studio; see Processing Options Properties Page (Report Manager).
You can run a report either on demand or as a snapshot. The following section describes each approach.
Running Reports On Demand
You can specify that a report query a data source each time a user runs the report, resulting in on-demand reports that contain the most up-to-date data. A new instance of the report is created for each user who opens or requests the report; each new instance contains the results of a new query. With this approach, if ten users open the report at the same time, ten queries are sent to the data source for processing.
Running Reports On Demand From Cache
To enhance performance, you can specify a report (and data) to be cached temporarily when a user runs the report. The cached copy is subsequently available to other users who access the same report. With this approach, if ten users open the report, only the first request results in report processing. The report is subsequently cached, and the remaining nine users view the cached report.
Cached reports are removed from the cache at intervals that you define. You can specify intervals in minutes, or you can schedule a specific date and time to empty the cache. For more information, see Caching Reports (SSRS).
Running Reports From Snapshots
A report snapshot is a report that contains layout information and data that is retrieved at a specific point in time. You can run a report as a report snapshot to prevent the report from being run at arbitrary times (for example, during a scheduled backup). A report snapshot is usually created and subsequently refreshed on a schedule, allowing you to time exactly when report and data processing will occur. If a report is based on queries that take a long time to run, or on queries that use data from a data source that you prefer no one access during certain hours, you should run the report as a snapshot.
A report snapshot is stored in a report server database, where it is subsequently retrieved when a user or process (such as a subscription) requests the report. When a report snapshot is updated, it is overwritten with a new instance. The report server does not save earlier versions of a report snapshot unless you specifically set options to add it to report history. For more information, see Create, Modify, and Delete Snapshots in Report History.
Not all reports can be configured to run as a snapshot. You cannot create a snapshot for a report that prompts users for credentials or uses Windows integrated security to get data for the report. If you want to run a parameterized report as a snapshot, you must specify a default parameter to use when creating the snapshot. In contrast with reports that run on demand, it is not possible to specify a different parameter value for a report snapshot when the report is open. Choosing a different parameter value would result in a new report processing request, which is not allowed.
In some cases, configuring an on-demand report to run as a snapshot can deactivate subscriptions. The following condition will cause a report server to deactivate existing subscriptions that were defined when the report was configured to run on demand:
The report uses query parameters, and you select a specific value as the default parameter to meet the requirements for running the report as a snapshot.
Existing subscriptions are configured to use parameter values that differ from the default parameter value that you specified for the snapshot.
When this condition exists, the report server will disable the subscription the next time the subscription is scheduled to run. To reactivate the subscription, open and then save the subscription. When you open the subscription, the report server updates the subscription parameter values to those specified for the snapshot. For more information about subscriptions, see Subscriptions and Delivery (Reporting Services).