Sync Table List

Sync Table List area

The users can check a list of tables that are synchronized for this instance.

Add Table button

  • A modal appears that allows the users to dynamically add synchronization tables.

Schema List

  • The users can check the schema of a table that is registered as a synchronized table.

  • The users can filter Schema list to check a list of synchronized tables.

Search and Delete

  • The users can search by filtering the items the users want to search for.

  • The users can remove it from the synchronization table.

Table List

The users can check a list of tables that are registered as synchronized tables.

Item
Description

Schema

The Schema of the table.

Table

The name of the table.

Registered Time

The time when the table was registered.

Details

The Description and Index information of the table.


Sync Table List example

Add Table

1. Setting Sync Table

Select the Schema and Table in each DB that the users want to set the synchronization target table.

2. Setting Column Mapping

The users can set up Column Mapping for a synchronized table.

By default, ProSync assumes that the columns in the source table and the columns in the target table have the same properties.

If there are attributes that don't match, such as different column names, or if there are columns to exclude from synchronization, the users can specify them explicitly at that stage.

Note

If the column is a Key Column, it cannot be specified as EXCEPT.

3. Setting Skip Rule

The users can set a synchronization to skip depending on the value of one of the synchronization tables.

By default, ProSync synchronizes over all column values.

If there are values to skip based on columns in the synchronization, the users can set a condition with a comparison statement at that step.

Note

The Comparison selection range may vary depending on the Column Type, and the users cannot set the Skip Rule if the users specified Column Mapping in the previous step.

4. Setting Initial Load

If the data exists in a table in Source, the users can set whether it is initially loaded or not.

Item
Description

Initial Load

Sets whether to initially load or not.

Force Migration

Truncates the data that exists in the Target table. Initial load requires that there is no data in the Target table, so the users should select this option if data exists in the Target table.

Note

Initial loading has the following limitations.

  1. Not supported if Target DB is Oracle.

  2. Unable to register if REPLAY_THREAD_CNT in Apply is 1 or less.

  3. Cannot register if Column Mapping is enabled (Except processing or mapping different column names).

  4. Initialization is not affected by Skip Rule even if Skip Rule is specified.

5. DCR Options

The users can set DCR options to resolve conflicts in data during ProSync two-way synchronization. For more information, refer to the "ProSync manual".

Item
Description

None

DCR option is not set.

SOURCE

Sets the DCR option based on the Source Table.

TARGET

Sets the DCR option based on the Target Table.

MIN/MAX

Sets the DCR option with the MAX/MIN value of the column by specifying one column. When a conflict occurs, it is a setting for whether to reflect the MAX/MIN criteria in the column, and a Default Value is required if the Column Value is NULL.

Last updated