A report server can keep a copy of a processed report and return that copy
when a user opens the report. This practice is called caching. Caching can
shorten the time required to retrieve a report if the report is large or is
accessed frequently. If the server is rebooted, all cached instances are
reinstated when the ReportServer service comes back online.
However, this introduces a problem when your users want to see the most
up-to-date report. Your users won't be aware of the caching facilities and they
will think there are some problems with the report.
To control the caching facilities of Reporting Services, you need to
configure the "Report Execution Properties" which can be accessed by
- Open the report you want to configure (unfortunately, you have you
configure the report one by one)
- Click on the "Properties" tab on top of the report and then click on
"Execution" link on the left hand side menu
- You will see the following screen with different processing modes
Normally, the default setting will give you the most up-to-date report;
however depending on your environment, you may want to provide caching and
specify a expiry time so you have more control.
Another tip is, you can ask your users to close and re-open the web browser
to reset their sessions in order to get most up-to-date report.