Inthis case, the UPDATE does not update anything.
Therow to be updated differs in one or more of its columns Ifone
ofthe values expected to be present has been changed by some other user,
anupdate conflict occurs.
Atremote databases, the update takes place regardless of the values in the
row.
Atthe consolidated database, SQL Remote allows conflict resolution
operationsto take place. Conflictresolution operations are held in a
triggeror stored procedure, and run automatically when a conflict is
detected.
InAdaptive Server Anywhere, the conflict resolution trigger runs before
theupdate, and the update proceeds when the trigger is finished. In
AdaptiveServer Enterprise, the conflict resolution procedure runs after
theupdate has been applied.
Atable without a primary key or uniqueness constraint refers to all
columnsin the WHERE clause of replicated updates When two
usersupdate the same row, replicated updates will not update anything
anddatabases will become inconsistent. All replicated tables should have
aprimary key or uniqueness constraint and the columns in the constraint
shouldnever be updated.
Replication of procedures
Anyreplication system is faced with a choice between two options when
replicatinga stored procedure call:
Replicatethe procedure call A corresponding procedure is executedat
thereplicate site, or
Replicatethe procedure actions The individual actions (INSERTs,
UPDATEs,DELETEs and so on) of the procedure are replicated.

SQL Remote replicates procedures by replicating the actions of a procedure.

Theprocedure call is not replicated.
Replication of triggers
Triggerreplication in SQL Remote is different for the Adaptive Server
EnterpriseMessage Agent and the Adaptive Server Anywhere Message
Agent.
Triggerreplication from
AdaptiveSer ver
Enterprise
FromAdaptive Server Enterprise, trigger actions are replicated. Youmust
ensurethat triggers are not fired in the remote Adaptive Server Anywhere
databases. If the trigger were fired, its actions would be executed twice.
80