Database Reference
In-Depth Information
Null Delivery Provider : This option is only used to preload the cache, which
we'll cover later on in this chapter.
The following screenshot shows a list of the offline file formats available with
Reporting Services 2012. For more information about these file formats, please see
the following TechNet article at http://technet.microsoft.com/en-us/library/
ms154606.aspx .
Subscriptions can be standard or data-driven. For standard subscriptions, all of the
input parameters for the report (for example, Sales Territory and Fiscal Period )
and the subscription (for example, recipient e-mail addresses and delivery file
format) must be known and supplied at the time the subscription is created. With
data-driven subscriptions, the values for parameters and delivery information are
queried from a relational source when the schedule executes. This makes data-driven
subscriptions ideally suited for delivering popular reports to a large list of recipients
in a variety of formats with different runtime parameter values—especially if the list
of recipients changes frequently.
While data-driven subscriptions offer a great deal of flexibility, they
can be a bit complex to create and configure properly. Therefore,
this task is usually taken on by a small handful of power users or
members of the IT department.
Report snapshots
The purpose of a snapshot is to reduce the load on the source system(s) and to
reduce the time a report consumer waits for a long-running report to execute on
demand. The basic idea is that a report is executed at some point in time, prior to
when it is actually needed by the business. A copy of the execution results is stored
as a snapshot on the report server. Then, at some point in the future, when users
execute the same report, the request is satisfied from the existing snapshot instead of
having to reprocess the entire report, which would involve sending another query to
the source system(s) and processing the results again.
 
Search WWH ::




Custom Search