Skip to main content Skip to complementary content

Store changes

These settings are only available when the Store changes replication mode is enabled.

On update

Information noteThis setting is not relevant for SaaS application sources as changes are applied as INSERT operations.

Select Store before and after image to store both the pre-UPDATE data and the post-UPDATE data. When not selected, only the post-UPDATE data will be stored.

Change table creation

If change table exists when full load starts: Select one of the following to determine how to load the Change Tables when Full Load replication starts:

  • Drop and create change table: The table is dropped and a new table is created in its place.
  • Delete old changes and store new changes in existing change table: Data is truncated and added without affecting the table metadata.
  • Keep old changes and store new changes in existing change table: Data and metadata of the existing Change table are not affected.

Table header columns

The Change Table header columns provide information about Change Processing operations such as the type of operation (e.g. INSERT), the commit time, and so on. If you do not need all of this information, you can configure the landing task to create the Change Tables with selected header columns (or none at all), thereby reducing their footprint in the target database..

Information noteYou cannot remove additional columns or restore columns while a task is running. To change your initial selection, you first need to stop the task, then modify your selection, and finally reload the target tables.

For a description of the header columns, see Change Tables.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!