Import Query Tracking (Aggregate Storage)

The MaxL import query_tracking statement helps you import query tracking data from a text file to an Essbase aggregate storage (ASO) cube.

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

When an ASO 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.

Keep in mind the following prerequisites before importing query tracking data:

Query tracking must be enabled and working for an ASO cube.
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.
Query tracking data for the cube must have been exported to a text file on the Essbase Server. Do not edit the text file with the exported query data.

Syntax

Description of the illustration imp_qry_tracking_as.gif

Keywords

You can use MaxL import query_tracking to import ASO query tracking information the following ways. The minimum application permission required to import query tracking data is Database Manager.

import query_tracking DBS-NAME from server file...: Import query data to the specified aggregate storage cube from the specified file. For FILE-NAME, specify the name of the text file that contains the query data to import. By default, the file is created in the cube directory, or whichever Essbase Server directory the administrator has specified for FILEGOVPATH.
import query_tracking DBS-NAME from file...: You can omit the server keyword, but the result is the same.

Note:

Query tracking and query tracing are different.

Query tracking enables you to capture 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. Related MaxL statements include:

import query_tracking
export query_tracking
alter database enable query_tracking
query database appname.dbname get cube_size_info

Query tracing helps you monitor Essbase query performance metrics for block storage cubes (including hybrid mode). It is off by default. If you enable it, Essbase logs metrics in a trace report. Related configuration parameters: TRACE_REPORT, QUERYTRACE, QUERYTRACETHRESHOLD, LONGQUERYTIMETHRESHOLD.

Example

import query_tracking ASOsamp.Basic from server file 'query_data_aso_sample.txt';

Imports the query data from the named file in the cube directory (or whichever directory the administrator has specified for export files) to the ASOsamp.Basic cube.