Data messages

Full Load (Replicate transfers the existing records from source table)

REFRESH – insert of a record during Full Load stage.

CDC (Replicate transfers the changes from source table)

INSERT – insertion of new record

UPDATE – update of existing record

DELETE – deletion of a record

A monotonically increasing change sequencer that is common to all change tables of a task.

Use this field to order the records in chronological order.

Applicable to CDC operations.

The original change UTC timestamp.

Applicable to CDC operations.

The source CDC stream position.

Applicable to CDC operations.

The ID of the transaction that the change record belongs to.

Use this field to gather all changes of a specific transaction.

Applicable to CDC operations.

Indicates which data columns were changed in the source table.

The change mask is a string of hexadecimal digits, representing a bitmask of data columns in little-endian order. The bit position in the change mask is based on the ordinal of the column in the metadata message of that table.

This means that if there are 10 data columns, they occupy bits 0 to 9 in the bitmask.

If UPDATE mask is 0B hexadecimal, which is 1011 binary – it means that the columns at ordinals 1, 2 and 4 were changed.

The following describes the bit semantics:

• For INSERT records, all the inserted columns have the associated bits set.
• For DELETE records, only primary-key (or unique index) columns have the associated bits set. This allows an applier to construct a DELETE statement without having to find the primary key fields from another source.
• For UPDATE records, each column with a changed value will have the associated bit set.

Indicates which data columns are present in the message. Usually, this will include all of the table columns.

The column mask is a string of hexadecimal digits, representing a bitmask of data columns in little-endian order. The bit position in the column mask is based on the ordinal of the column in the metadata message for that table.

This allows the applier to distinguish a null value that is the actual value of the column, from a null value that represents a column which could not be replicated from the source database.

The Schema ID. This will only be displayed if the Include external Schema IDheader check box is selected.

As the Schema ID changes whenever a DDL is performed on the source table, consumer applications can use this information to determine if the message schema has changed.

The sequence number of the current operation in the transaction.

This can be used to determine the order of operations within a transaction.

"True" indicates that it is the final record in the transaction whereas "False" indicates that not all of the records have been processed.