Crystal Reports Performance

Apr 17, 2011   //   by Dan B   //   How to, Other  //  No Comments
Not UsefulUseful (No Ratings Yet)
Loading ... Loading ...

Below are a few simple design decisions that can dramatically improve the performance of your Dekho Crystal Reports.  These suggestions have come from a recent experience with a particular client, where report times were reduced from approximately 1 minute down to just a few seconds.

Optimal Report Design Decisions

  • KISS – CRs should be as simple as possible – avoid sub-reports and formula logic.
  • Push as much of the processing to the DBMS as possible – either through Stored Procedures or through views that aggregate report data. Less CR processing on the app server = more resources for other Dekho requests equating to greater scalability.
  • Limit the number of tablesviews in the report and use indexed fields where possible
  • In a production environment, ensure that the Dekho Crystal Report logging level is set to ERROR.

Hope this helps,

Leave a comment

four − = 3