reporting services doesn't support paging datasets.
the entire query must be retrieved from the database before the rendering
can starts.
Generally, for long running reports, we use the snapshot functionality and
execute the report in the morning and save it as a new snapshot, the user
will access the snapshot which is already rendered.
or optimize your queries
or create your own web application to support some paging
[quoted text, click to view] "bojannikic" <bojannikic@discussions.microsoft.com> wrote in message
news:04AC1742-F9EF-4BA9-9EB0-42A371D57F08@microsoft.com...
> Hi Experts,
>
> We have a stored procedure that takes a long time to execute. It takes
> 4:45
> sec.
>
> When we execute the report it shows "Reporting is generated!" for 5
> minutes.
> Is there a way to generate dataset asynchronously as it is being executed?
> Show first page fast and keep getting data into a dataset. Or do all
> datasets need to be completed before any page of the report is shown.
>
> Thank you very much in advance!
>
> Bojan
On Sep 21, 1:00 pm, bojannikic <bojanni...@discussions.microsoft.com>
[quoted text, click to view] wrote:
> Hi Experts,
>
> We have a stored procedure that takes a long time to execute. It takes 4:45
> sec.
>
> When we execute the report it shows "Reporting is generated!" for 5 minutes.
> Is there a way to generate dataset asynchronously as it is being executed?
> Show first page fast and keep getting data into a dataset. Or do all
> datasets need to be completed before any page of the report is shown.
>
> Thank you very much in advance!
>
> Bojan
If this is a report that must show current data then you can have the
snapshot refreshed frequently throughout the day. You could also have
the stored procedure update a table frequently throughout the day.
Then simply report off the data in the table.
Matt Penner
