Automatically Optimizing Techniques - Intergraph Smart Materials - Version 10.1 - Administration & Configuration - Hexagon

Intergraph Smart Materials Classic Administration (10.1)

Language
English
Product
Intergraph Smart Materials
Subproduct
Classic
Search by Category
Administration & Configuration
Smart Materials/Smart Reference Data Version
10.1

An optimizing function automatically performs the tips mentioned above.

Several Occurrences of Tables

Depending on the where condition definition, one table could occur several times in the FROM-part of the view definition with its corresponding joins in the WHERE-condition. The optimizing function suppresses these superfluous mappings so that each table occurs only once.

Pyramidal Structure

The optimizing function builds the view definition using a pyramidal structure based on the number of entries as follows:

The FROM-part entries are sorted using the number of rows contained in a table beginning with the table with the highest number of rows.

The WHERE-part of the definition starts with the constraints made in the second block of the A.60.06 screen. The joins of tables are then sorted beginning with the table that contains the fewest number of joins.

Common Sub-Expressions

Multiple OR-combined comparisons like:

(CG_GROUP_CODE = 'X' OR
CG_GROUP_CODE = 'Y' OR
CG_GROUP_CODE 0 'Z' )

on the A.60.06 screen are automatically changed to:

CG_GROUP_COLDE IN ('X', 'Y', 'Z').

Checking for Foreign Keys on the A.60.07 screen

When creating the view on A.60.06, the Where Conditions procedure searches for the column name to build the joins between the tables. In other words, the procedure searches for the column name(s) of the primary key for table 1, and then searches for columns with the same name in table 2. If a match is found, the join is built. If a foreign key exists between these tables, Oracle uses the index table for building the join. If the program does not find a foreign key, an alert box displays the message:

MAR-10549: No foreign keys found: <table1>, <table2>, …

You can save the attribute although no foreign key is found.