Hi! I've implemented a telerik report within a website. The data for the report is being generated through a stored procedure in a MS SQL Server database which takes one parameter. I have an aspx page with a Report Viewer control. The dataset creation and databinding occurs in the code behind for the aspx page with the Report Viewer. On another aspx page there is a button which loads the page with the Report Viewer.
The report loads without error and the data is present. However the first time the report loads it takes several seconds before being displayed. Any report displayed after that loads in less than a second. Note - The value of the parameter for the stored procedure changes depending on what item the user decides to "view" so the data in the report varies depending on which item is selected.
Is there any way to speed up the initial loading of the report?
Thanks!
The report loads without error and the data is present. However the first time the report loads it takes several seconds before being displayed. Any report displayed after that loads in less than a second. Note - The value of the parameter for the stored procedure changes depending on what item the user decides to "view" so the data in the report varies depending on which item is selected.
Is there any way to speed up the initial loading of the report?
Thanks!
1 Answer, 1 is accepted
0
Hello Amy,
The ReportViewer is a complex control that contains several standard asp.net controls inside its toolbar that are loaded in the page. Additionally every report instantiation will cache the whole report in the server's memory and this is per session. This cache is not only data, but the whole report being processed - and every report item has numerous properties.
Thus it is normal that the initial load would take longer than subsequent changes to the report datasource.
All the best,
Steve
the Telerik team
The ReportViewer is a complex control that contains several standard asp.net controls inside its toolbar that are loaded in the page. Additionally every report instantiation will cache the whole report in the server's memory and this is per session. This cache is not only data, but the whole report being processed - and every report item has numerous properties.
Thus it is normal that the initial load would take longer than subsequent changes to the report datasource.
All the best,
Steve
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Public Issue Tracking
system and vote to affect the priority of the items