If cost-based optimization is enabled and you provide values for the map and join column properties, the Actuate SQL compiler creates an index when 100 rows are materialized in memory during query execution. You can change the number of materialized rows that triggers indexing using the pragma MinRowsForIndexing.
If cost-based optimization is disabled, or you do not provide values for the map and join column properties, an index is created for materialized rows if a suitable column is available.
Specifying the number of materialized rows that triggers indexing for an information object has no effect on queries that use the information object.
You can specify the number of materialized rows that triggers indexing for all information object queries by setting the BIRT iServer configuration variable Minimum rows to trigger creation of an index during materialize operation. For more information about Actuate iServer configuration variables, see
Configuring BIRT iServer.
