skip to content »

Ssrs linked reports not updating

ssrs linked reports not updating-2

Sometimes you might have to be a bit clever in order to ensure all parameters have a default.For instance, if the default is always “current fiscal period” that continually changes, you can make this happen with an intermediary hidden parameter – it might just take a bit of extra time to think up a good solution.

ssrs linked reports not updating-62ssrs linked reports not updating-82ssrs linked reports not updating-86ssrs linked reports not updating-21

In contrast, users access report execution snapshots from folders the same way that they access live reports.If you’re only using Report Execution snapshots for this report, you’ll probably want to store them in the history.However, if you happen to be using both Report Execution and Report History snapshots for the same report, you might want to leave it unchecked so they don’t get mixed up – i.e., if you are doing both, then the schedules will differ for a reason.An introduction to using snapshots in SQL Server Reporting Services, including an explanation of the differences between a “Report Execution Snapshot” and a “Report History Snapshot.” 1. Most reports typically are executed on demand – i.e., the query in the dataset runs and the report is displayed at the time the report is requested by the user. If you have a long-running query that cannot be tuned further, one option you might look into is caching.This is the default in “Processing Options” within Report Manager (accessed via the “Manage” menu option). With this method, the first user that executes the report will wait for the report to render.In the case of report execution snapshots, no visual cue exists to indicate to users that the report is a snapshot.” Let’s say on the Processing Options page you checked the radio button to “render this report from a report snapshot.” Then you scheduled it on the Snapshot Options page. You can even view the report within the Report History just fine.

However, you click on the report name (i.e., the normal way to run a report) you get a message: Why the message? What happened is with the setup just described, a Report History snapshot now exists but no Report Execution snapshots exists.

As you are perusing the options when you “Manage” a report, you will notice there’s two different schedules associated to snapshots.

First, there’s the scheduling options on the “Processing Options” page: Secondly, there’s scheduling options on the “Snapshot Options” page: Initially you might say “huh? The key here is that there’s really two kinds of snapshots…

Let’s say you schedule your Report Execution snapshot within the Processing Options.

The report runs fine, but you don’t see it within Report History.

The rest of this blog entry focuses on using snapshots.