Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
arkiboys
Master Smack Fu Yak Hacker
1433 Posts |
 Posted - 2008-01-14 : 05:03:19
|
| Hi,In a .net application there is a link that brings up a SSRS report.I have noticed that if it is the first time this report is requested i.e. Application has just been opened and the report button is clicked, then it takes a while to get this report to appear on the screen. But if this report is requested again (i.e. for the second time or more) then it only takes a few moments for the report to appear on the screen.So it seems that only the first time the report is requested it takes a longer time to get this report. Is there a way to reduce this initial load of the report?Thanks |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2008-01-14 : 06:16:38
|
| This may be because the report has caching property enabled.Go to report manager and check the execution settings to see if caching is enabled.If report is having parameters then try running report for a different set of params. Are you using sp to retrieve data from db? if yes, have a look into SP to get an idea of amount of data retrieved and its performance and try filtering unwanted data/optimising performance of SP. |
 |
|
|
arkiboys
Master Smack Fu Yak Hacker
1433 Posts |
Posted - 2008-01-14 : 06:54:48
|
quote:
Originally posted by visakh16
This may be because the report has caching property enabled.Go to report manager and check the execution settings to see if caching is enabled.If report is having parameters then try running report for a different set of params. Are you using sp to retrieve data from db? if yes, have a look into SP to get an idea of amount of data retrieved and its performance and try filtering unwanted data/optimising performance of SP.
Caching is NOT enabled. |
|
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2008-01-14 : 08:31:23
|
quote:
Originally posted by arkiboys
quote:
Originally posted by visakh16
This may be because the report has caching property enabled.Go to report manager and check the execution settings to see if caching is enabled.If report is having parameters then try running report for a different set of params. Are you using sp to retrieve data from db? if yes, have a look into SP to get an idea of amount of data retrieved and its performance and try filtering unwanted data/optimising performance of SP.
Caching is NOT enabled.
If you are using SP, can you try running it in query analyser and see how it performs? |
|
|
|
|
|
|
SSRS from .net