Data Partitions

Replication Server Data Assurance Option 15.7.1 SP100 allows large tables to be split into logical partitions.

For maximum performance, you can run each logical partition in parallel on a database with multiple engines. The data partitions can be run in smaller groups, if DA is configured to run fewer comparisons at the same time.

Note: When you run a comparison with a new compareset for the first time, DA runs the comparison with a single partition to gather partition information for subsequent runs.

The SQL where clause on the compareset key columns defines the upper and lower partition boundaries. The boundary key values are sampled for a compareset when a comparison that uses it is run for the first time. These boundary samples are stored in the Data Assurance System Database (DASD).

On subsequent runs, any comparison that uses the same compareset uses those boundary samples to split a table into as many logical partitions as required. Each time a comparison is run, DA collects the new boundary samples for the compareset in use, and updates them in the DASD.

To view and manage the data partitions and boundary samples, use:

show boundary and drop boundary commands to view or delete the data partition boundary samples for each compareset.
NUM_PARTITIONS comparison option to set the number of data partitions for a comparison.
PART column in the monitor job and show job command's result set to view the data partition number for a comparison.

See Row Comparison Job Commands and Data Partition Commands in the Replication Server Data Assurance Users Guide.