Databases Reference
In-Depth Information
While access to a cached report has been taken care off by storing the credentials of
the user creating the cache, the permissions to change the cache properties must also
be covered by security. These are secured by permissions that are only given to the
some of the roles such as Content Manager , Publishers , and so on. Follow the link
http://msdn.microsoft.com/en-us/library/ms155927.aspx to learn more.
The Report cache is created by the user but it can be created automatically by
Execution Snapshot. Execution Snapshot can be used to create a cache on a scheduled
basis. This feature needs to be turned on for each report. Execution Snapshot lends
itself for handling cache expiry by proper scheduling.
How does a user know that he has got a cached report? Well, the time of execution
is the clue. If the date and time of execution is not current and it is not a snapshot,
then it is a cached copy.
Report processing options
Here is an image of the Processing Options available on Report Manager in
SQL Server 2012.
 
Search WWH ::




Custom Search