Reporting Services Rendering is Slow

I use the web service as well as intergrated url link to display, but both
display the same characteristics. The first run is extreemly slow. We
could be talking up to 1 minute to generate a pretty basic report.
When the same report with a differnet parameter or even a different report
is run the display is immediate.
The server it sits on has not been rebooted, but if i run the same report
the next day then it runs as if its the first time its run.
Is there some kind of setting I've missed in IIS or SRS that is obviously
unloading all the compiled referneces to SRS. I understand that .net
application are slow on first execution due to compiling etc.
Can anyone help?the first time you access Reporting Service, IIS must compile the webpages.
a w3wp process starts and compile the page and then start the rendering.
after some times, the application pool is killed to released the resources
on the server.
So go in your application pool (in IIS) and change the recycle parameters.
and also you can create a scheduled task to wakeup Reporting Services.
"Namshub" <Ricchard.Pullen@.Southend.nhs.uk.RemoveMyspam> wrote in message
news:Oi#tWk8iHHA.4516@.TK2MSFTNGP03.phx.gbl...
>I use the web service as well as intergrated url link to display, but both
>display the same characteristics. The first run is extreemly slow. We
>could be talking up to 1 minute to generate a pretty basic report.
> When the same report with a differnet parameter or even a different report
> is run the display is immediate.
> The server it sits on has not been rebooted, but if i run the same report
> the next day then it runs as if its the first time its run.
> Is there some kind of setting I've missed in IIS or SRS that is obviously
> unloading all the compiled referneces to SRS. I understand that .net
> application are slow on first execution due to compiling etc.
> Can anyone help?
>
>|||maybe you should stop using MDB as a database
"Namshub" <Ricchard.Pullen@.Southend.nhs.uk.RemoveMyspam> wrote in message
news:Oi%23tWk8iHHA.4516@.TK2MSFTNGP03.phx.gbl...
> I use the web service as well as intergrated url link to display, but
both
> display the same characteristics. The first run is extreemly slow. We
> could be talking up to 1 minute to generate a pretty basic report.
> When the same report with a differnet parameter or even a different report
> is run the display is immediate.
> The server it sits on has not been rebooted, but if i run the same report
> the next day then it runs as if its the first time its run.
> Is there some kind of setting I've missed in IIS or SRS that is obviously
> unloading all the compiled referneces to SRS. I understand that .net
> application are slow on first execution due to compiling etc.
> Can anyone help?
>
>|||Snotty but not the reason. Note that it is the first time that he has
problems, not subsequent times. This is totally an IIS issue and the fact
that asp.net application (which is what RS is) gets unloaded.
Detailed instructions for solution is: Go to IIS Manager, under Applocation
Pools node, right click "DefaultAppPool" in which the Reporting Server work
process is running, select properties. On "Performace" tag, you will see,
by default, the app pool will shut down if > being idle for 20 min. You can
extend this time to 8x60min 480min, so that the app pool will not shut down
for a regular working day. However, the first report reader of the day,
will hit the delay. You may schedule a dummy report at beginning of a work
day for this.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Aaron Kempf" <akempf@.dol.wa.gov> wrote in message
news:uAzPTfdjHHA.208@.TK2MSFTNGP05.phx.gbl...
> maybe you should stop using MDB as a database
>
> "Namshub" <Ricchard.Pullen@.Southend.nhs.uk.RemoveMyspam> wrote in message
> news:Oi%23tWk8iHHA.4516@.TK2MSFTNGP03.phx.gbl...
>> I use the web service as well as intergrated url link to display, but
> both
>> display the same characteristics. The first run is extreemly slow. We
>> could be talking up to 1 minute to generate a pretty basic report.
>> When the same report with a differnet parameter or even a different
>> report
>> is run the display is immediate.
>> The server it sits on has not been rebooted, but if i run the same report
>> the next day then it runs as if its the first time its run.
>> Is there some kind of setting I've missed in IIS or SRS that is obviously
>> unloading all the compiled referneces to SRS. I understand that .net
>> application are slow on first execution due to compiling etc.
>> Can anyone help?
>>
>

Reporting Services Rendering

We use Reporting Services for most of our reporting needs internally. However, we do have several products that we ship out into the field that run off local databases. These applications require reporting but often are not big enough for SQL Server and rarely run on a server with IIS.

Since MS has made .RDL an open xml standard does anyone know if there are any client rendering engines being developed? We would like the ability to develop all of our reports in .RDL and have them rendered in Reporting Services or in our standalone apps that run off MSDE or Access. Currently this is not possible. But, I think that someone could write a client renderer (like Crystal Reports has) to allow the use of .RDL files off a local data source without SQL Server and Web Services.

Thanks for any info on the subject.

SmokeAs far as I understand it, the .rdl files can only be put onto a SQL Server. Basically, it seems that Microsoft wants to give you the ability to access those reports through just about anything (ASP.Net, jsp pages) that can connect to an XML web service, but the actual files themselves are proprietary to just SQL Server boxes with the reporting services installed. Have you ever thought about creating those reports on a server and connecting to them through those programs across the internet and encrypting them?