Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Other than running reports on demand, there are two specific options: Running from a Cached report and running from a Snapshot.</p> <p>You can see details on all of this in <a href="http://technet.microsoft.com/en-us/library/ms159241%28v=sql.100%29.aspx" rel="nofollow">Setting Report Processing Properties</a>.</p> <p><strong>Caching</strong></p> <p>From Books Online:</p> <blockquote> <p>To enhance performance, you can specify a report (and data) to be cached temporarily when a user runs the report. The cached copy is subsequently available to other users who access the same report. With this approach, if ten users open the report, only the first request results in report processing. The report is subsequently cached, and the remaining nine users view the cached report.</p> </blockquote> <p>So here you can see that it is a specific user action that causes a stored report to be created.</p> <p>See <a href="http://technet.microsoft.com/en-us/library/ms155927%28v=sql.100%29.aspx" rel="nofollow">Report Caching in Reporting Services</a>.</p> <p><strong>Snapshots</strong></p> <p>From Books Online:</p> <blockquote> <p>A report snapshot is a report that contains layout information and data that is retrieved at a specific point in time. You can run a report as a report snapshot to prevent the report from being run at arbitrary times (for example, during a scheduled backup). A report snapshot is usually created and subsequently refreshed on a schedule, allowing you to time exactly when report and data processing will occur. If a report is based on queries that take a long time to run, or on queries that use data from a data source that you prefer no one access during certain hours, you should run the report as a snapshot.</p> </blockquote> <p>Here you can see that these are these are generally set up on a regular schedule, i.e. independent of user activity.</p> <p>See <a href="http://technet.microsoft.com/en-us/library/ms156325%28v=sql.100%29.aspx" rel="nofollow">Creating, Modifying, and Deleting Snapshots in Report History</a>.</p> <p>In this case it seems like <strong>Snapshots</strong> might be your best option so you have more control of when the stored report is created. The main issue with Snapshots is that they need either stored credentials or an unattended execution account so might not be possible in all cases.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload