The applied subcommand describes operations recorded in the database, including:
Row updates
Row inserts
Row deletes
Executions of applied stored procedures (request stored procedures use the execute subcommand)
Modifications to text or image data
Truncate table or partition
The syntax for the applied subcommand is:
distribute command_tags applied [owner=owner_name]
{'table'.rs_update
yielding before param_list after param_list |
'table'rs_insert yielding after param_list |
'table'.rs_delete yielding before param_list |
'table'.function_name [param_list]
yielding after param_list before param_list |
'table'.rs_datarow_for_writetext
yielding datarow column_list |
'table'.rs_writetext
append [first] [last] [changed] [with log]
[textlen=100] column_list}|
‘table’.rs_truncate [partition_name[, partition_name]...] yielding}
For syntax and description of command_tags, see “Command tags”.
table is the name of the database table to which the operation was applied. It must be enclosed in quotation marks.
Replication Server uses table to associate the command with a replication definition. Beginning with Replication Server version 11.5 and version 200 LTL, if the tag @mode=0x08 is set, Replication Server also associates the owner name with the replication definition. The create replication definition command’s with all tables named table_identifier clause determines how table is mapped to a replication definition:
If the replication definition has a with all tables named table_identifier or with primary table named table_identifier clause, table above is matched to the table_identifier or with the primary table named.
If the with all tables named table_identifier clause and the with primary table named table_identifier clauses were omitted, then table above is the name of the replication definition.
RepAgent does not need to be aware of replication definitions. It can use the table name on the data source.
