Friday, March 30, 2012

Reporting Services Tuning

A couple of questions related to Reported Services tuning that I hope
someone might be able to give me a clue about....
1) In the Reporting Services Books Online, I have found a lot of
information on performance monitoring, but very little on performance
tuning. Is any additional information available, perhaps a whitepaper? Or
perhaps I am just missing something that is in the BOL?
2) An immediate question we have that perhaps someone can answer is, is
there any way to give On Demand reports a higher execution priority than
Scheduled reports? A particular concern is that a shared schedule, say "End
of month" processing, might become very popular and have a large number of
reports subscribed to it. These reports might then overload the server,
adversely effecting the execution time of On Demand reports.
Any enlightenment would be greatly appreciated.
Thanks,
BobOne thing to keep in mind. A snapshot of the report/data can be saved. So,
you can schedule to run at night every night and then save x days of
reports. Or you can run weekly and save 10 weeks of data (you specify how
many snapshots to save). This report or a link to it can be emailed out. To
me that is what makes the most sense, run the scheduled reports in off time
and then you will have no concern about the On Demand reports.
Bruce L-C
"Bob Hug" <rhug@.brassring.com> wrote in message
news:O6LK84QZEHA.3944@.tk2msftngp13.phx.gbl...
> A couple of questions related to Reported Services tuning that I hope
> someone might be able to give me a clue about....
> 1) In the Reporting Services Books Online, I have found a lot of
> information on performance monitoring, but very little on performance
> tuning. Is any additional information available, perhaps a whitepaper? Or
> perhaps I am just missing something that is in the BOL?
> 2) An immediate question we have that perhaps someone can answer is,
is
> there any way to give On Demand reports a higher execution priority than
> Scheduled reports? A particular concern is that a shared schedule, say
"End
> of month" processing, might become very popular and have a large number of
> reports subscribed to it. These reports might then overload the server,
> adversely effecting the execution time of On Demand reports.
> Any enlightenment would be greatly appreciated.
> Thanks,
> Bob
>sql

No comments:

Post a Comment