1. Configuration Reference for Oracle Essbase
  2. Essbase Configuration Settings
  3. Config Settings List
  4. TARGETASOOPT

TARGETASOOPT

This Essbase configuration setting potentially optimizes certain large queries to an aggregate storage database across a transparent partition.

Use the TARGETASOOPT configuration setting to potentially optimize large queries (from Smart View or other grid clients, MDX, or Report Writer) to an aggregate storage database across a transparent partition when the source outline and target outline are identical in the partition region definition area.

Syntax

TARGETASOOPT [appname] TRUE | FALSE

  • appname—Optional. Application name. If you specify a value for appname, the setting applies to all databases in the specified application. If you do not specify an application, the setting applies to all applications and databases on the Essbase Server.

  • FALSE—The default. Optimization is not enabled, even if queries match the required criteria (see Description).

  • TRUE—Optimization is enabled for queries that match the required criteria (see Description).

    When TARGETASOOPT is TRUE, Essbase completes the following steps:

    1. When the partition is next validated, automatically determines if the partition region definition outlines are identical on the source and target databases

    2. If the partition region definition outlines are identical, the query is sent in the compact format from the target database to the source database.

You must restart Essbase Server to initialize any change to the configuration file.

Description

TargetASOOpt enables an alternate (compact) format for sending a query (from Smart View or other grid clients, MDX, or Report Writer) to an aggregate storage source database, and hence may speed up large queries between databases that match the following criteria:

  • Databases are transparently partitioned (for example, to enable write-back for aggregate storage databases)

  • Source is an aggregate storage database

  • Partitioned area definitions in the source and target are identical (for example in the Sample Basic database, if the partition region definition is@idesc("100"), then the outline hierarchies below Time, Market, Measures, Scenario, and 100, must be identical on the source and target databases)

  • Source outline and target outline are identical

Notes

If at query time the source and target outlines have been modified after the last validation, even if the partition region definition outlines are still identical, TARGETASOOPT is dissabled for the query. To enable TARGETASOOPT for the query, you must revalidate the partitions.

Example

TARGETASOOPT TRUE

See Also

TARGETTIMESERIESOPT