What should you configure the report to do?

Your network contains a System Center 2012 Configuration Manager environment.
You create a report that lists compliance information.
You schedule the report to run every day at 20:00.
You need to ensure that on Friday, you can review the results of the report created on the previous
Monday.
What should you configure the report to do?

Your network contains a System Center 2012 Configuration Manager environment.
You create a report that lists compliance information.
You schedule the report to run every day at 20:00.
You need to ensure that on Friday, you can review the results of the report created on the previous
Monday.
What should you configure the report to do?

A.
Use caching.

B.
Use a shared schedule.

C.
Render on Friday.

D.
Use snapshots.

Explanation:
http://technet.microsoft.com/en-us/library/ms156325.aspx
Creating, Modifying, and Deleting Snapshots in Report History
Report history is a collection of report snapshots. You can maintain report history by adding and
deleting snapshots, or by modifying properties that affect report history storage. You can create
report history manually or on a schedule.
Further information:
http://technet.microsoft.com/en-us/library/ms157447.aspx
Cache a Report (Report Manager)

One way to improve performance is to configure caching properties for a report. When a report is
cached, a copy of the rendered report is saved for a short period of time. The first user who requests
the report must wait for all processing to complete before viewing the report. Subsequent users
who request the report within the caching period can view it right away because processing has
already occurred.



Leave a Reply 1

Your email address will not be published. Required fields are marked *


MGJG

MGJG

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. If you require a more predictable caching strategy, you should create a report snapshot.

https://docs.microsoft.com/en-us/sql/reporting-services/report-server/caching-reports-ssrs