Reporting Services performance

When I first go to the Report Manager, it takes a long time to load the web
page (15-30 seconds). After that it loads in a acceptable amount of time.
is there a way to configure it so that the page loads more quickly the first
time?
--
Message posted via http://www.sqlmonster.comI think what you will find is happening is that the Reporting Service
is "starting up" the first time you access it. We are having the same
problem and I am currently trying to find an answer. There is an
article on Microsoft's website talking about Anti-virus causing it to
restart frequently. But this doesn't seem to be that problem. The
server "stops" after a certain amount of inactivity and then takes a
while to start up when it's next accessed.
I'll post here if I find an answer.
Chris Harvie|||Here's the scoop. After a time of inactivity
First, a quick little hack. Create a very simple report, have it autoexecute
every x minutes (I do 5 minutes). I just leave this up. The delay goes away.
Then there are these suggestions from another poster which I have included
below. Personally, I had a report that I look at frequently anyway so I have
not tried this. I know my suggestion will work. If you try the below post
back on your success or failure:
Bruce Loehle-Conger
MVP SQL Server Reporting Services
>>>>>>>>>>>>>>
If you are running Windows 2003 server for your IIS reportserver, then this
is a simple issue - I'll explain what happens:
The report service engine, once it is idle for more than the default 20
minutes, the worker process is shutdown.
This is controlled by IIS.
Open up the Internet Information Services (IIS) Manager
Expand the server node then the application pools.
On my IIS machine, I created an application pool dedicated to the
reportserver & reportmanager virtual webs.
But anyways, for the application pool that the reportserver is pointing to
if you left everything to their defaults will be the DefaultAppPool.
Right click the default app pool and select properties.
There are two things that are checked by default - On the recycling tab
there is a checkbox for recycling worker processes - it is currently set to
1740 minutes (29 hours). Leave it.
The other one is on the performance tab - which is the one you are
interested in changing...
See the "Idle Timeout" section and increase the number of minutes to be 8
hours a typical working day - 8*60 = 480 minutes.
Next, to be sure the "morning person" that runs the first report doesn't get
the delay, set up a schedule for either a dummy or adhoc report to fire off
like at 6am so that the report component worker processes get loaded.
I hope this helps you.
There is no need to have a report fire off every minute to keep things
alive - it is just that the report service was "unloaded" and needed to load
back up.
=-Chris
If you are running Windows 2003 server for your IIS reportserver, then this
is a simple issue - I'll explain what happens:
The report service engine, once it is idle for more than the default 20
minutes, the worker process is shutdown.
This is controlled by IIS.
Open up the Internet Information Services (IIS) Manager
Expand the server node then the application pools.
On my IIS machine, I created an application pool dedicated to the
reportserver & reportmanager virtual webs.
But anyways, for the application pool that the reportserver is pointing to
if you left everything to their defaults will be the DefaultAppPool.
Right click the default app pool and select properties.
There are two things that are checked by default - On the recycling tab
there is a checkbox for recycling worker processes - it is currently set to
1740 minutes (29 hours). Leave it.
The other one is on the performance tab - which is the one you are
interested in changing...
See the "Idle Timeout" section and increase the number of minutes to be 8
hours a typical working day - 8*60 = 480 minutes.
Next, to be sure the "morning person" that runs the first report doesn't get
the delay, set up a schedule for either a dummy or adhoc report to fire off
like at 6am so that the report component worker processes get loaded.
I hope this helps you.
There is no need to have a report fire off every minute to keep things
alive - it is just that the report service was "unloaded" and needed to load
back up.
=-Chris
>>>>>>>>
<Harv013@.gmail.com> wrote in message
news:1129825242.427488.89690@.o13g2000cwo.googlegroups.com...
>I think what you will find is happening is that the Reporting Service
> is "starting up" the first time you access it. We are having the same
> problem and I am currently trying to find an answer. There is an
> article on Microsoft's website talking about Anti-virus causing it to
> restart frequently. But this doesn't seem to be that problem. The
> server "stops" after a certain amount of inactivity and then takes a
> while to start up when it's next accessed.
> I'll post here if I find an answer.
> Chris Harvie
>

Reporting Services Performance

Hi All,
Does anyone has some information regarding the kind of server you need
for getting better performance from the Reporting Services (both for
Database and IIS portion of RS?
Thanks in advance,
SuhaibIt depends on what you would like to do. For instance, is cashing reports an
option for you or do you need real time data to be displayed? What will be
the render medium, image, html, pdf? How many concurrent sessions on average
will there be on the server?
These are the first questions that you need to answer. Take a look at
Kent's presentation and also in TechEd there was a session dedicated to RS
infrastructure. By the way, has anybody received DVD's of TechEd
presentations?
http://www.tegels.org/rs4ti.zip
Regards,
Cem
"Suhaib Khan" <skhan@.faicorp.com> wrote in message
news:u22BmvrWEHA.1652@.TK2MSFTNGP09.phx.gbl...
> Hi All,
> Does anyone has some information regarding the kind of server you need
> for getting better performance from the Reporting Services (both for
> Database and IIS portion of RS?
> Thanks in advance,
>
> Suhaib
>

Reporting Services Performance

Hi,

I'm just wondering if anyone else has had any problems with reporting services when generating reports.

I have a rather large report (approx 5000 rows) and to be fair there are alot of links to other tables. However it takes 5-10 minutes to generate this report.

If I manually pull the data from the database, perform the aggregations and all the table joins, it takes under 10 seconds to complete and I seriously doubt that rendering the table to put the data in takes 10 minutes to do.

Any Ideas?An update on this,

I just tried creating a report without all the information in the other tables, so the report is now taking 5128 rows from one table and displaying all the columns. This took 5 minutes to generate.

Again any Ideas on why this is taking so long?|||

Do all significant data processing on the server, particularly joins/unions/selections/projections.

Limit the report engine to data processing that's easy for it to do without additional roundtrips to the server, such as running totals, grouping, subtotaling, etc.

I'll bet your 5 minute report will become instantaneous by pushing the data processing to the server, where it is best handled. Views and stored procedures are your friends.

This approach also reduces the dependency on the report writer, so that you can use other report engines to render the same report data regardless of the capabilities and quirks of their client-side data engines.

|||

I have the following task to investigate: which server will need more resources at the time of reports execution using Reporting Services 2005

In a standard deployment you will have two servers: A. Report Server

B. SQL Sever Database

When using enbedded code / Expression in a report: example: Sum, Count, etc. Who will execute this action? It is the Report Server or the SQL Server?

The main idea is to determine who will need more resources in order to have the best performance in the reports execution.

Thanks

Reporting Services Performance

Hi,

I'm just wondering if anyone else has had any problems with reporting services when generating reports.

I have a rather large report (approx 5000 rows) and to be fair there are alot of links to other tables. However it takes 5-10 minutes to generate this report.

If I manually pull the data from the database, perform the aggregations and all the table joins, it takes under 10 seconds to complete and I seriously doubt that rendering the table to put the data in takes 10 minutes to do.

Any Ideas?An update on this,

I just tried creating a report without all the information in the other tables, so the report is now taking 5128 rows from one table and displaying all the columns. This took 5 minutes to generate.

Again any Ideas on why this is taking so long?|||

Do all significant data processing on the server, particularly joins/unions/selections/projections.

Limit the report engine to data processing that's easy for it to do without additional roundtrips to the server, such as running totals, grouping, subtotaling, etc.

I'll bet your 5 minute report will become instantaneous by pushing the data processing to the server, where it is best handled. Views and stored procedures are your friends.

This approach also reduces the dependency on the report writer, so that you can use other report engines to render the same report data regardless of the capabilities and quirks of their client-side data engines.

|||

I have the following task to investigate: which server will need more resources at the time of reports execution using Reporting Services 2005

In a standard deployment you will have two servers: A. Report Server

B. SQL Sever Database

When using enbedded code / Expression in a report: example: Sum, Count, etc. Who will execute this action? It is the Report Server or the SQL Server?

The main idea is to determine who will need more resources in order to have the best performance in the reports execution.

Thanks

Reporting Services Implementation

We are just now looking at implementing Reporting Services, and I would like
to pose a few questions.
1. What are the issues (performance, etc)/dangers (security, etc) of
installing Web Services on a SQL Server?
2. What, if anything, can be done to minimize these issues?
3. I would like to get a feeling for how most shops are setting up RS. Are
you putting it with an existing SQL installation, or are installing
separately?
4. Do you have success/horror stories concerning RS?
SteveOne thing you don't mention is whether this is an intranet or internet
scenario. Many DBAs are very hesitant to have anything other than the
database engine running on the server. Not just for performance but for
security. My feeling is that for intranet applications DBAs better adjust
because IIS will be happening on the same server for many scenarios of which
RS is one of them. If you have the CPU bandwidth then RS running on the same
server is no big deal from a performance issue. The main issue is that you
should harden IIS. Plus use integrated security.
If an internet application then I would suggest that the data (versus the
object caching) should be behind the firewall. Note that RS needs SQL Server
for its object caching. You can have SQL Server local on the server just for
that and the data can be somewhere else.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"hoo-t" <hoo-t@.discussions.microsoft.com> wrote in message
news:C1456869-61D8-4646-AE15-318CAAA9D972@.microsoft.com...
> We are just now looking at implementing Reporting Services, and I would
like
> to pose a few questions.
> 1. What are the issues (performance, etc)/dangers (security, etc) of
> installing Web Services on a SQL Server?
> 2. What, if anything, can be done to minimize these issues?
> 3. I would like to get a feeling for how most shops are setting up RS.
Are
> you putting it with an existing SQL installation, or are installing
> separately?
> 4. Do you have success/horror stories concerning RS?
> Steve
>|||Bruce,
Thanks for your response. The implementation that is currently being looked
at would be intranet, as would most if not all our implementations. However,
I wanted to leave that issue open in order to get the broadest viewpoint, as
was presented with your post.
As you said, IIS is being installed for reasons other than Reporting
Services. In fact, most of our SQL Servers do have it installed, but the Web
Services portion is disabled. Reporting Services requires Web Services,
which opens up a whole new can of worms!
Steve
"Bruce L-C [MVP]" wrote:
> One thing you don't mention is whether this is an intranet or internet
> scenario. Many DBAs are very hesitant to have anything other than the
> database engine running on the server. Not just for performance but for
> security. My feeling is that for intranet applications DBAs better adjust
> because IIS will be happening on the same server for many scenarios of which
> RS is one of them. If you have the CPU bandwidth then RS running on the same
> server is no big deal from a performance issue. The main issue is that you
> should harden IIS. Plus use integrated security.
> If an internet application then I would suggest that the data (versus the
> object caching) should be behind the firewall. Note that RS needs SQL Server
> for its object caching. You can have SQL Server local on the server just for
> that and the data can be somewhere else.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "hoo-t" <hoo-t@.discussions.microsoft.com> wrote in message
> news:C1456869-61D8-4646-AE15-318CAAA9D972@.microsoft.com...
> > We are just now looking at implementing Reporting Services, and I would
> like
> > to pose a few questions.
> > 1. What are the issues (performance, etc)/dangers (security, etc) of
> > installing Web Services on a SQL Server?
> > 2. What, if anything, can be done to minimize these issues?
> > 3. I would like to get a feeling for how most shops are setting up RS.
> Are
> > you putting it with an existing SQL installation, or are installing
> > separately?
> > 4. Do you have success/horror stories concerning RS?
> >
> > Steve
> >
>
>