Muokkaa

Jaa


Cache a shared dataset

One way to improve performance is to configure caching properties for a shared dataset. When a shared dataset is cached, a copy of the query results is saved for a specified period of time. The first user who requests a report that uses the shared dataset must wait for the query results and all processing to complete before viewing the report. Subsequent users who request the report within the caching period experiences improved performance because the query and processing already occurred. You can also specify a cache refresh plan to run the query and cache the results until the specified cache expiration.

Users running reports based on a shared dataset or cache refresh plans create the query cache and in both cases, the cache is available, based on the cache expiration options.

There are restrictions on the types of shared datasets that you can cache. For example, the query results can't be cached if the data varies based on the user identity. Similarly, caching isn't feasible if data is retrieved using the security token of the user who requests the report. For more information, see Cache Shared Datasets (SSRS) and Caching Reports (SSRS).

To schedule the expiration of a cached report

  1. Start Report Manager (SSRS Native Mode).

  2. In Report Manager, navigate to the shared dataset for which you want to set caching properties, hover over the item, and select the arrow.

  3. In the menu, choose Manage.

  4. In the left frame, select Caching.

    Note

    If you see the error, "Credentials used to run the shared dataset are not stored", the cache shared dataset option is disabled. You need modify the data source to store credentials or modify the shared dataset to use a different data source that does store credentials.

  5. Select Cache share dataset.

  6. Select the option to expire the cache after 30 minutes. You can also choose for the cache to expire on a specified schedule.

  7. Select Apply.