Export Query Tracking (Aggregate Storage)

The MaxL export query_tracking statement for ASO mode helps you export query tracking data from an Essbase aggregate storage cube to a text file.

Query tracking captures user retrieval statistics against an aggregate storage cube, enabling Essbase to make view-based optimizations to improve the performance of aggregations.

When an aggregate storage cube is refreshed or restarted, query data is not persisted in the cube. As an optimization technique, before refreshing or restarting, you can export query tracking data to a text file. To rebuild aggregate views after a refresh or restart, import the query tracking data from the text file. Essbase uses the query data to select the most appropriate set of aggregate views to materialize.

Before exporting query tracking data, query tracking must be enabled and working.

Note:

Query tracking is enabled by default for aggregate storage cubes. To check whether it's enabled, you can confirm by running the following MaxL statement (example is for ASOSamp Basic cube):

query database ASOSamp.Basic get cube_size_info;

If you need to enable query tracking, use the alter database (aggregate storage) statement with the enable query_tracking grammar.

The MaxL export query_tracking statement for ASO mode helps you export query tracking data from an Essbase aggregate storage database to a text file.

Permission required: Database Manager.

Syntax

Description of the illustration exp_qry_tracking_as.gif

You can use export query_tracking in the following ways.

Keywords

export query_tracking <dbs-name> to server file...: Export query data from the specified aggregate storage cube to the specified file. Unless the administrator has specified a different export location, the file is created in the <Application Directory>/app/appname/dbname folder. (If you do not know where <Application Directory> is in your environment, see Environment Locations in the Essbase Platform for an explanation.)
export query_tracking <dbs-name> to file...: You can omit the server keyword, but the result is the same.

Notes

Do not edit the text file with the exported query data.
Query tracking and query tracing are different. Query tracking captures user retrieval statistics against an aggregate storage cube, so that Essbase can make view-based optimizations to improve the performance of aggregations. It is on by default. Query tracing helps you monitor Essbase query performance metrics for block storage and hybrid cubes. It is off by default. If you enable it, the information you want to trace is written to the application log and/or a separate tracing log. Related configuration parameters: TRACE_REPORT, QUERYTRACE.

Example

export query_tracking ASOsamp.Basic to server file 'query_data_aso_sample.txt';

Exports query data from the ASOsamp.Basic database to the named file. The export location is the cube directory (ASOSamp/Basic/), or whichever Essbase Server directory the administrator has specified for FILEGOVPATH.