We have a report that can get to be very large, with some 10,000 rows. When we try to display it in a browser, the first page, which is the group header section containing heading information, renders fine. The second page, which is the group footer section containing the 10,000+ rows of detail, always hangs, and we only see a blank page.
There is no way to limit the number of records returned. Our customers will want to see the entire report, and be able to look through it. How do we get it to display?
1 Answer, 1 is accepted
0
Hi Craig,
When the report needs to display a large amount of data it will require additional computer resources (powerful CPUs, memory). On top of that, other factors that can affect report performance need to be considered such of the report layout, complexity of data calculations (aggregates, conditional formatting), rendering media, size of the generated document (in pages).
You can test exporting a report programmatically instead of displaying it in the viewer. However, the machine will still need to have the resources required by the reporting engine for generating reports.
Our strong recommendation is to reduce the amount of rows that need to be retrieved from the data source by applying report parameters and data source parameters.
Also, check if the report has Data items and if it does, check if you set only the DataSource property of those Data items without setting the report's DataSource property.
It might be that both report's and inner data item's DataSource properties are set and the data gets duplicated - Data Binding Problems - Repeating data.
Other suggestion for optimizing report performance can be found in Performance Considerations help article.
Regards,
Katia
Telerik by Progress
When the report needs to display a large amount of data it will require additional computer resources (powerful CPUs, memory). On top of that, other factors that can affect report performance need to be considered such of the report layout, complexity of data calculations (aggregates, conditional formatting), rendering media, size of the generated document (in pages).
You can test exporting a report programmatically instead of displaying it in the viewer. However, the machine will still need to have the resources required by the reporting engine for generating reports.
Our strong recommendation is to reduce the amount of rows that need to be retrieved from the data source by applying report parameters and data source parameters.
Also, check if the report has Data items and if it does, check if you set only the DataSource property of those Data items without setting the report's DataSource property.
It might be that both report's and inner data item's DataSource properties are set and the data gets duplicated - Data Binding Problems - Repeating data.
Other suggestion for optimizing report performance can be found in Performance Considerations help article.
Regards,
Katia
Telerik by Progress
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 Feedback Portal and vote to affect the priority of the items