Posted by: Ashish Kumar | April 16, 2009

Performance issues for Siebel Actuate Reports Series -1

AshishDedicated to Rachana Agarwal , who irritated me a lot to write this Actuate page..


Performance issues for Actuate Reports can occur due to a variety of factors. This technical note discusses these factors and concludes with some general trouble shooting steps to isolate which of these factors may be affecting your report performance.
The following topics are detailed in this technical note.
• Report Design
• Reports Server
• Network
• Siebel Object Manager
• Volume of Data
• Troubleshooting Steps

Report Design

The report design can have a large impact on the performance of a report. Consider the following points to assess impact on any slow reports.
Search Specification on Business Component
A report processes the records retrieved from the business component. A report can be configured to process only some of the records that are returned by the business component. For example, both male and female records may be returned by the business component, but the report only wants to process the male records. You can configure the report to process records in this way by doing the following:
• Adding code into the Fetch method of the datastream. In this situation all records are retrieved into the report, and only then are they filtered. For this reason, the report may take longer to complete if a large amount of records are retrieved.
• Setting the search specification on the relevant business component.
• Setting the search specification property of the reports object. NOTE: The entire business component is queried without considering the user interface (UI) query when the report is run using this approach.
When specifying search specifications, especially on large tables, it is important to use key column fields whenever possible that match the performance indexes defined against the underlying base table. For best performance the specifications should not only cover all of the key columns for a desirable index, but also cover them in the exact index order. This encourages the database engine to use the index and prevents unnecessary physical sorts in temporary tables. Always be aware that search specifications affect the WHERE clause of the SQL statement generated.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s


%d bloggers like this: