Your network contains a System Center 2012 Configuration Manager 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.
Explanation:
http://technet.microsoft.com/en-us/library/bb522786.aspxPerformance, Snapshots, Caching (Reporting Services)
Report server performance is affected by a combination of factors that include hardware, number of
concurrent users accessing reports, the amount of data in a report, and output format. To
understand the performance factors that are specific to your installation and which remedies will
produce the results you want, you will need to get baseline data and run tests.
General principles to consider include the following:
Report processing and rendering are memory intensive operations. When possible, choose a
computer that has a lot of memory.
Hosting the report server and the report server database on separate computers tends to provide
better performance than hosting both on a single high-end computer.
If all reports are processing slowly, consider a scale-out deployment where multiple report server
instances support a single report server database. For best results, use load balancing software to
distribute requests evenly across the deployment.
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.
If all reports process slowly in a specific format (for example, while rendering to PDF), consider file
share delivery, adding more memory, or choosing a different format.
To find out how long it takes to process a report and other usage metrics, review the report server
execution log.
http://technet.microsoft.com/en-us/library/ms155927.aspx
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.