Skip to content

Reporting engines

Types of reporting engine

Standard engine

CCH Tagetik Financial Reporting's standard reporting engine runs complex SQL queries based on the choice of filters. The data are transformed and refined directly as part of the SQL queries.

Every transformation (on-the-fly conversion, segment, etc.) is run directly in the database.

This engine is used under the following conditions:

• If minimum transformations must be applied to the block of data to be extracted.

• If a SAP HANA database is being used.

• If a large number of filters have been applied.

In-memory engine

The in-memory engine is a reporting engine that optimises the read/write process performed by standard engines. It has the following advantages:

  • It ensures greater scalability: queries run by the in-memory engine are simpler and make it possible to shift the computational burden from the database manager to the application server.
  • It reduces the runtime of forms. Especially for forms that use advanced reporting functionalities like segments, FX rates and time-dependence, the query generated by the standard engine takes a long time. The in-memory engine takes advantage of the benefits linked to a simpler query and server application concurrency.

By changing the Reporting engine option from Standard to In memory, or vice versa, in the form settings (see Form options window), the system warns the user that the concurrency settings will be reset. The concurrency settings are in fact linked to the reporting engine type. While for the standard engine the system tends to keep the settings defined in the configuration step, for the in-memory engine the system sets the degree of concurrency to one, because the in-memory engine has concurrency mechanisms that mean that a high degree of concurrency is superfluous.

When this engine is used, the following information must be specified: Block size rows, Size of the data loading threadpool and Size of the data processing threadpool (see Run settings details).