SAP Knowledge Base Article - Public

1678041 - Crystal Report using native Pervasive connectivty performs slower than in previous versions

Symptom

After upgrading a report from Crystal Reports 8.5 or earlier to Crystal Reports 9.0 or later notice slower performance when reading data from a remote Pervasive data file via native connectivity

Environment

  • Crystal Reports 2008 (12.2.0.290)
  • Pervasive 10.3
  • Data on a different machine than Crystal Reports

Reproducing the Issue

  1. Create a report in Crystal Reports 8.5 or earlier using Pervasive native connectivity to a database on another machine
  2. Open the report in Crystal Reports 9.0 or later such as Crystal Reports 2008 and refresh the data
  3. Notice that it takes much longer to refresh the data than it did in Crystal Reports 8.5 and earlier

Cause

  • Crystal Reports data connectivity architecture changed significantly in Crystal Reports 9.0 creating two side effects for Pervasive native connectivity
    • Indexes are not being used for the joining of remote tables
    • More API calls are being made to the Pervasive engine due to the generic nature of the new architecture for file-based databases

Resolution

After examining the problem under ADAPT Problem Report "ADAPT01565036 - TE:Slow Native Connection to Pervasive" the Product Owner has determined that resolving this issue in the native connectivity will require a significant amount of development work which cannot be justified at this time.

Customers encountering this performance problem when connecting to Pervasive data over the network are asked to use one of the following solutions.

  • Switch to using the Pervasive ODBC driver
  • Run Crystal Reports on the same machine as the Pervasive data file

Keywords

  • Crystal Reports
  • Native Connectivity
  • Native Driver
  • Pervasive
  • Performance
  • Slow
, KBA , BI-RA-CR , Crystal Reports designer or Business View Manager , Problem

Product

Crystal Reports 2008 V1 ; SAP Crystal Reports 2011