The following table lists and describes the SQL statements that are supported for data linkage by Datareplicator.

Table 1-7 SQL statements supported for data linkage by Datareplicator

SQL type	Supported for data linkage	Limitations
INSERT	Y	Data linkage is not supported for a table for which the WITHOUT ROLLBACK option is specified.
UPDATE	Y	Data linkage is also performed for any column that is not specified in the SET clause of the UPDATE statement (a column that is not updated) as if it has been updated by the same value. However, data linkage is not performed for an unupdated column if it has any of the following data types: VARCHAR type (256 bytes or greater) NVARCHAR type (128 characters or greater) MVARCHAR type (256 bytes or greater) BLOB type BINARY type Abstract data type (SGMLTEXT, FREEWORD, XML)
DELETE	Y	Data linkage cannot be performed for a table for which the WITHOUT ROLLBACK option is specified.
PURGE	Y	Data linkage cannot be performed for a table for which the WITHOUT ROLLBACK option is specified. Data linkage cannot be performed when a table subject to extraction is divided and placed in multiple BESs. For details about the processing when the PURGE statement is executed on a table that has been divided and placed in multiple BESs, see the prg_eventno operand in 5.4 Transmission environment definition.
Other SQL statement	N	--

Legend:

Y: Data linkage is supported with some limitations.

N: Data linkage is not supported.

Note:

If multiple rows in the source database are updated by a single SQL statement, the target Datareplicator issues as many SQL statements as there are rows updated in the source database (data linkage is performed in units of updated rows, not in units of SQL statements).