Extended text-maintained staging infrastructure for incremental update

A configuration option is available in Version 9.7 to add a staging infrastructure that enables capturing changes that are not recognized through the triggers in the regular log table. If this option is enabled, updates are captured through a trigger in the regular log table, inserts and deletes are captured in the text-maintained staging table.

This configuration option is enabled by default for range-partitioned tables and disabled for non-partitioned tables. Adding the text-maintained staging infrastructure has a critical impact on the availability and status of the base table for various database operations.

The impact of the text-maintained staging infrastructure is similar to adding a Materialized Query Table (MQT) with deferred refresh. Even though the text-maintained infrastructure does not maintain data in a MQT, the staging table causes corresponding behavior to that shown for a MQT staging table.

For example, after a LOAD insert, the tables require integrity processing to enable subsequent database operations on the base table.

If tables are only updated with database commands that affect all rows in the table, for example with LOAD REPLACE, adding the extended staging infrastructure does not provide a benefit, instead, the index should be re-created.