Q Replication and Event Publishing Q Replication and Event PublishingThe no load option is appropriate when the source and target tables are synchronized before any Q subscriptions become active and replication begins.
When you specify the no load option for a Q subscription, the Q Apply program begins applying transactions to a target table as soon as the Q subscription becomes active.
If you choose the no load option, make sure that the values of the primary key or unique index from the source table are also present in the primary key or unique index of the target table.
You might specify no load when adding a large number of new tables during a period of relative inactivity in the source and target databases or subsystems. After you quiesce the source tables, you load the target tables, and then activate the Q subscriptions.
You might also specify a no load option if you back up a source database and then restore the database on the target server.
