Table Rules Define Which Objects Will Be Compared

If a DB process instruction has no table rules, every instance of the object will be compared when the compare process runs (and this might be exactly what you want to do). However, assume you only want to compare business process scripts whose prime key starts with CI_ . To do this, you need a "table rule" on the DB process instruction associated with the SCRIPT maintenance object. Table rules contain SQL snippets that are incorporated into the WHERE clause into the SQL statement used to select objects. For example, the following table rule will limit the selection of scripts to that that start with CI_.

Figure 1. DB Process Instruction Table Rule

Table rules may be specified on any DB process instruction for any table within the related maintenance object. However, most of the time, they are only specified on a Primary DB process instruction's Primary table.

CAUTION:

Specifying additional WHERE clauses may introduce inefficient data access. If you are comparing large amounts of data, it's a good idea to compose table rules that are supported by an index.

Note: Inner Joins . If you specify a table rule on a Child table within the DB process instruction, that table is joined with its recursive parent tables in the resulting SQL. Use the SQL viewer (a push button on the DB process instruction page) to make sure that the resulting SQL is really what you want.

Fastpath: Refer to Defining Database Process Instruction Options for more information on setting up DB process instruction table rules.