Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.
A user deletes a row (with a given primary key value.) A second user updates or deletes the same row at another site. In this case, the second statement fails, as the row is not found.
To replicate UPDATE and DELETE statements correctly, you must include all of the primary key columns in the article.
When an UPDATE or a DELETE statement is replicated, SQL Remote uses the primary key columns to uniquely identify the row being updated or deleted. All tables being replicated must have a declared primary key or uniqueness constraint. A unique index is not enough.
The primary key columns are used in the WHERE clause of replicated UPDATE and DELETE statements. When a table has no primary key, the WHERE clause refers to all columns in the table. See Replicating INSERT and DELETE statements.
|Discuss this page in DocCommentXchange.
Send feedback about this page using email.
|Copyright © 2009, iAnywhere Solutions, Inc. - SQL Anywhere 11.0.1|