Showing posts with label runs. Show all posts
Showing posts with label runs. Show all posts

Saturday, February 25, 2012

Report History in SQL Reporting Service

Hi,

I am using SQL Server 2005 Reporting service. I am working on a report. I have made several subscriptions for it. Report runs according to subscription. SQL Server Reporting service also offers functionality to save report histories. Now how can I configure it so that whenever report runs according to its subscription, a history should be automatically saved?

If in case it is not possible by some automatic process then is there any way to set multiple schedules for history of the single report like multiple subscriptions can be set for single report.

Waiting for your response. Thanks in advance.

Regards,
Sulman.

Under the History Properties of the report, you need to select the option to:
Store all report execution snapshots in history.

There are also other options to indicate how many snapshots you want to keep, as well as creating snapshots on a regular schedule.|||Thanx, J Quick

Yes there is an option in Hisotry properties "Store all report execution snapshots in history". But let me clear how it works.

On the Execution property page there are two option.
1. "Render this report with the most recent data"
This option means that whenever the report will be executed, it will get fresh data from database by making query on it.
2. "Render this report from an execution snapshot"
This option means that an execution snapshot of report will be saved either once when the Apply button is pressed or it will keep on updating depending upon schedule. But at one time there will be only one execution snapsho. And whenever the report will be executed, it will be rendered from that execution snapshot and not from the fresh data of database.

Now i come to History property mentioned above to "Store all report execution snapshots in history". It will work only when the execution property of report is set to "Render this report from an execution snapshot". And if execution snapshot is scheduled to be updated then each time the execution snapshot will update it will also be saved in history as history snapshot. So for this history property to work, we have to sacrifice the updated and fresh data. But in my case, i have to get fresh data every time and also i want to save the history of that executed report. Try to think on this line.

Anyhow i appreciate your effort. Thanx again.

Sulman.
|||

>> "It will work only when the execution property of report is set to "Render this report from an execution snapshot".

I don't think the statement above is correct, but I could be wrong since it has been some time since I tried it.

As I recall, the options to "Render this report with the most recent data" and "Store all report execution snapshots in history" are on different property pages and aren't mutually exclusive.

Tuesday, February 21, 2012

Report Hangs

I am running SQL Server 2005 Reporting Services. I have a report that runs
with an Access database as the data source. Occasionally the report will
hang at the "Report is being generated" screen. The screen never times out
even if left for hours. Once one job fails any other attempts to run this
report hang too. I can't find anything useful in any of the logs. FYI,
this report runs successfully most of the time.
How can I purge pending or running jobs from the queue? Does anyone have
any suggestions on what the problem may be? Is there anyway for me to force
a timeout on a report run?
Thanks in advance for any help you can provide.On Jun 6, 11:04 am, Rob <R...@.discussions.microsoft.com> wrote:
> I am running SQL Server 2005 Reporting Services. I have a report that runs
> with an Access database as the data source. Occasionally the report will
> hang at the "Report is being generated" screen. The screen never times out
> even if left for hours. Once one job fails any other attempts to run this
> report hang too. I can't find anything useful in any of the logs. FYI,
> this report runs successfully most of the time.
> How can I purge pending or running jobs from the queue? Does anyone have
> any suggestions on what the problem may be? Is there anyway for me to force
> a timeout on a report run?
> Thanks in advance for any help you can provide.
The only things I can think of are to either kill the rs.exe process
in the task mgr -or- to reset IIS (via: 'iisreset' at the command
prompt). As far as why this happens, I am not sure; though I would
think that it could be related to high demand on the database or
possibly IIS or rs.exe choking up. Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant

Report Formatting Differently on different servers with same RDL

This is a good one:

Same RDL, 2 different servers. I run the report on my computer and export to PDF, it prints properly. When the customer runs the report on their server (SSRS 2K5 SP1, same as mine), they get it displayed differently. The columns on the report extend to the next page and the lines are thicker.

Is this a formatting issue on the customer's PC? It uses standard fonts (Tahoma, Sans-serif).

Any ideas?

maybe you are using a matrix on the report and the customer has different data (more data) that makes the matrix extend?

lines are thicker? I can't think of anything there unless it is the fonts, but you look ok with that.

|||

No, it is not a matrix report. It is a standard layout table that is 10 inches wide, it's set for landscape with .5in margins.

|||I did some more research and started a new report from scratch and the same issue occurs.