Your network contains a System Center 2012 R2 Configuration Manager Service Pack 1 (SP1) environment.
You create a report named Report1. Report1 is used by multiple users.
Users report that it takes too long to load Report1.
You need to reduce the amount of time it takes to load Report1.
What should you do?
A. Enable caching for the report.
B. Decrease the size of the ReportServer database.
C. Decrease the session timeout value for the Reports website.
D. Increase the size of the ReportServerTempDB database.
Correct Answer: A
Explanation/Reference:
Explanation:
http://technet.microsoft.com/en-us/library/bb522786.aspx
Performance, Snapshots, Caching (Reporting Services)
If a single report is processing slowly, tune report dataset queries if the report must run on demand. You might also consider using shared datasets that you can cache, caching the report, or running the report as a snapshot.
Note: Caching Reports (SSRS)
A report server can cache a copy of a processed report and return that copy when a user opens the report. To a user, the only evidence available to indicate the report is a cached copy is the date and time that the report ran. If the date or time is not current and the report is not a snapshot, the report was retrieved from cache. Caching can shorten the time required to retrieve a report if the report is large or accessed frequently. If the server is rebooted, all cached instances are reinstated when the Report Server Web service comes back online.
Caching is a performance-enhancement technique. The contents of the cache are volatile and can change as reports are added, replaced, or removed.
Reference: Performance, Snapshots, Caching (Reporting Services)
http://technet.microsoft.com/en-us/library/bb522786.aspx
