To build complex business objects and ensure data integrity, Optim™ solutions gather data by
traversing the tables in your database. For faster performance, limit
the amount of data that is gathered by limiting the number of traversals
or by excluding unnecessary rows.
Limiting Traversals
The traversal method
is set in the Access Definition Editor on the Relationship tab.
- When Option 1 is enabled, Optim solutions
gather the record from the parent table that relates to the processed
record.
- When Option 2 is enabled, Optim solutions
gather all records from the child table that relate to the processed
record.
By default, Option 1 is enabled and Option 2 is disabled.
In some cases, you want to enable Option 2 to capture a complete business
object. However, if you do not need to capture so much data for your
business objects, you might choose to leave Option 2 disabled for
faster performance.
For example, a database contains the following
tables:
- Table CUSTOMERS contains customer records.
- Table ORDERS contains order records.
- Table DETAILS contains detailed information about each order.
Table CUSTOMERS is a parent of table ORDERS, and table ORDERS
is a parent of table DETAILS. If you archive old orders, you want
to gather the customer records that relate to the orders that you
are archiving. However, you might not need to gather the order details
for each order. By default, Optim gathers
the customers that relate to the orders that you are archiving, but
does not gather the order details. For faster performance, you might
choose to use these default values. The order details are not archived,
but the archive process completes much more quickly.
Excluding Rows
For an archive or extract
process, exclude any rows with a relationship value equal to empty,
null, zero-length, or a specified numeric value. This option is set
in the Access Definition Editor on the Relationship tab.