7.9 High-Performance Configurations for Crystal

7.9.1 Increasing the Report Refresh Record Limit for Crystal Reports Server

Depending on the number of events that Crystal Reports is querying, you might get an error on the maximum processing time or maximum record limit. To set your server to process a higher number or an unlimited number of records, you must reconfigure the Crystal Page Server by using either the Central Configuration Manager or the Crystal Web Page.

Using the Central Configuration Manager to reconfigure the Crystal Page Server

  1. Click Start > All Programs > BusinessObjects 11 > Crystal Reports Server > Central Configuration Manager.

  2. Right-click Crystal Reports Page Server, then select Stop.

  3. Right-click Crystal Reports Page Server, then select properties.

  4. In the Command field in the Properties tab, at the end of the command line add:

    maxDBResultRecords <value greater than 20000 or 0 to disable the default limit>
    
  5. Restart the Crystal Page Server.

Using the Central Management Console to reconfigure the Crystal Page Server

  1. Click Start > All Programs > BusinessObjects 11 > Crystal Reports Server > .Net Administration Launchpad. Alternatively, open a Web browser and provide the following URL:

    http://<hostname_or_IP_of_web_server>/businessobjects/enterprise115/WebTools/adminlaunch/default.aspx
    
  2. Click Central Management Console.

  3. The System Name should be your host computer name. The Authentication Type should be Enterprise. If not, select Enterprise.

  4. Specify your username and password, then click Log On. Click Servers.

  5. Click <server name>.pageserver.

  6. In Database Records to Read When previewing or Refreshing a report, select Unlimited records. Click Apply.

    A prompt to restart the page server displays

  7. Click OK.

    You might be prompted for a login name and password to access the operating system service manager.

7.9.2 Using the Aggregration Service for Reports

To improve performance, the Top 10 reports that are included in the Sentinel Core Solution Pack query the summary tables instead of the events table. The summary tables contain counts over time for combinations of fields in the event data. This provides a much smaller data set for certain types of queries and results in much faster queries and report run time.

The Aggregation service is responsible for populating the summary tables with summarizations of all of the events in the events table. The Aggregation service only generates summarized data for summaries that are active. The following summaries are required by the Top 10 reports and are enabled by default:

  • EventDestSummary

  • EventSevSummary

  • EventSrcSummary

Summaries can be activated or disabled by using the Reporting Data configuration window in the Admin tab of Sentinel Control Center.

The Aggregation service also depends on the EventFileRedirectService component in the DAS Binary to feed the event data that it summarizes. Therefore, this component must be enabled in order for the Aggregation service to run properly. This component is enabled or disabled by modifying the status attribute of the EventFileRedirectService component in the das_binary.xml file to ON or OFF. By default, this component is ON.

For more information about EventFileRedirectService and the three aggregation summaries, see Report Data Configuration in Admin in the Sentinel 6.1 User Guide.

NOTE:Reports that query a large date range might take sometime to run. They can be scheduled instead of running interactively. For information about scheduling Crystal Reports, see Crystal BusinessObjects Enterprise 11 documentation and click the CRYSTAL REPORTS SERVER.pdf.

The above mentioned URL was current at the time of publication of the document.

7.9.3 Report Development

The Crystal Reports Developer can be used to create or modify Crystal reports. For custom developed reports, the following is recommended:

  • If the reports can utilize predefined aggregate tables, select the aggregate table that results in processing of the least amount of data.

  • Try to move most of the data processing to the database engine.

  • To reduce processing overhead on the Crystal server, minimize the amount of data to retrieve to the Crystal server.

  • Always write reports against the database views provided by Novell, instead of writing reports against the base tables.