1. Analytical Application Infrastructure User Guide
  2. System Configuration and Identity Management
  3. System Configuration
  4. Configuration
  5. Update Optimization Details

Update Optimization Details

  1. Select Optimization Details tab and update the details as tabulated:

    Figure 13-25 Optimization tab


    This illustration shows the Optimization tab, which enables you to specify Hints, Scripts, and Using ROWID instead of Primary Keys to optimize Merger statements.

    The Optimization details such as Hints, Scripts, and Using ROWID instead of Primary Keys can be specified to optimize Merge statements. The defined configurations are also fetched as Query Optimization Settings while defining Rule definition properties.
    The following table describes the fields in the Optimization tab.

    Table 13-15 Fields in the Optimization tab and their Descriptions

    Field Description
    Hint used for MERGE statement

    Specify the SQL Hint that can be used to optimize Merge Query.

    For example, “/*+ ALL_ROWS */”

    In a Rule Execution, Merge Query formed using definition level Merge Hint precede over the Global Merge Hint Parameters defined here. In case the definition level Merge Hint is empty / null, Global Merge Hint (if defined here) is included in the query.
    Hint used for SELECT statement

    Specify the SQL Hint that can be used to optimize Merge Query by selecting the specified query.

    For example, “SELECT /*+ IS_PARALLEL */”

    In a Rule Execution, Merge Query formed using definition level Select Hint precede over the Global Select Hint Parameters defined here. In case the definition level Select Hint is empty / null, Global Select Hint (if defined here) is included in the query.
    Script executed before MERGE statement

    Refers to a set of semicolon (;) separated statements which are to be executed before Merge Query on the same connection object.

    In a Rule Execution, Global Pre Script Parameters defined here are added to a Batch followed by Rule definition level Pre Script statements if the same has been provided during rule definition. However, it is not mandatory to have a Pre Script either at Global or definition level.
    Script executed after MERGE statement

    Refers to a set of semicolon (;) separated statements which are to be executed after Merge Query on the same connection object.

    In a Rule Execution, Global Post Script Parameters defined here are added to a Batch followed by Rule definition level Post Script statements if the same has been provided during rule definition. However, it is not mandatory to have a Post Script either at Global or definition level.
    User ROWID in ON clause of MERGE statement

    You can select the ROWID checkbox to create a Merge Statement based on specified ROWID instead of Primary Keys.

    In a Rule Execution, ROWID is considered while creating Merge Statement if Use ROWID checkbox is selected in either Global Parameters defined here or Rule definition properties.

    If Use ROWID checkbox is not selected in either Global Parameters defined here or Rule definition properties, then the flag is set to “N” and Primary Keys are considered while creating in Merge Statements.

  2. Click Save and save the Optimization details.