Refreshing the cache
Did you notice an issue with the previous recipe related to caching? I am sure that you have. The first issue is that it uses the cache continuously if the shared schedules set of expiring the cache is paused. Since the cache does not get expired, users will not get a fresh copy even after the scheduled time.
The second issue is, if the schedule set for expiring the cache is expired or not available, Reporting Services will not create a cache instance for the report again. Since Reporting Services does not to create the cache, performance of the report rendering becomes poor as it always needs to get the required data from the source.
We need to make sure that the caching we have enabled is continuously functioning even with ...
Get SQL Server 2016 Reporting Services Cookbook now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
