This is a migrated thread and some comments may be shown as answers.

Telerik Report hang up

1 Answer 143 Views
General Discussions
This is a migrated thread and some comments may be shown as answers.
Haitham M.
Top achievements
Rank 1
Haitham M. asked on 21 May 2012, 10:43 AM
Hello,

i am using Telerik Report v2008 with .Net Framework 4; i am facing problem when i retrieve large result from DB (using SQL Server 2008) the report takes long time and most time the IIS and machine hangs up.

i trace my code and discover the the problem when the report take datasource from .Net

Any Help

Regards,

Haitham 

1 Answer, 1 is accepted

Sort by
0
Steve
Telerik team
answered on 22 May 2012, 04:02 PM
Hello Haitham,

Thank you for the description of the problem. Unfortunately the provided information is insufficient for us to determine what is going wrong in your case and to get to the bottom of the problem we would need more than this:
  • What is the version of Telerik Reporting you use?
  • How many records do you get from your sql query?
  • How much time does it take for the above operation?
  • Have you tried to calculate how many pages would your report generate should it be able to render? If that number is bigger than 100, can you explain the goal of this report i.e. your business case?
  • Does the report render eventually if you leave it be or you get an exception. If the latter, what is the exception?
  • What are the specifics of the machine which renders the report - OS, RAM, CPU?

Handling reports (be it with large data or large number of report items) usually requires additional resources in terms of powerful CPUs, and enough memory to handle all the operations. As far as the processing time and consumed memory is concerned, the complexity of the report layout, the complexity of the data calculations (aggregates, conditional formatting),  the rendering media, the size of the generated document (in pages), and the capabilities of the underlying machine are crucial.

Also be aware that the purpose of reports is to transform information into "knowledge" and rendering hundreds of pages is not that kind of transformation, as in very rare cases anyone should go through a report that is more than 100 pages. In most cases users look for a specific information, so when you a high number of records, the best option would be to decrease their number by applying a filter with Report Parameters in order to minimize the chances of problems when you generate large reports and of course offer ability for your user to choose only desired information to be shown. Additionally you can check our Performance Considerations help article.
If your main goal is to show this data for web presentation only, we can suggest a grid control instead, moreover our RadGrid control exposes API for pdf, csv, word, excel exporting.

Greetings,
Steve
the Telerik team

BLOGGERS WANTED! Write a review about Telerik Reporting or the new Report Designer, post it on your blog and get a complimentary license for Telerik Reporting. We’ll even promote your blog and help bring you a few fresh readers. Yes, it’s that simple. And it’s free. Get started today >

Tags
General Discussions
Asked by
Haitham M.
Top achievements
Rank 1
Answers by
Steve
Telerik team
Share this question
or