Working with changes resulting from referential integrity

The following table summarizes key concepts related to referential integrity as it relates to the Log Master product:

Category

Information

Key concepts

Any log record that reflects an insert, update, or delete action contains a bit that indicates whether the action occurred as a result of a referential integrity (RI) constraint.
Log Master interprets the INCLUDE RI setting based only on the value of this RI bit. The product does not trace or discover RI relationships to determine which RI constraint caused the change.
The INCLUDE RI setting applies only to SQL output. Other types of output contain all selected log records (as if INCLUDE RI was set to YES).
When you generate UNDO SQL, the INCLUDE RI setting ensures that Log Master generates SQL statements in an order that accommodates RI constraints.

Impact

To capture a set of changes to one table, and all of the resulting RI changes in other tables, you must define your filter carefully. For more information, see INCLUDE RI example.
Set the INCLUDE RI value depending on how you intend to use with the selected changes. Adjust the setting depending on whether you are migrating data, backing out problem transactions, or performing other tasks. For more information, see INCLUDE RI recommendations.

This section contains the following topics:

Comments