Skip to Content

Mobilink Synchronization using SQL Anywhere 11 doesn't upload all deletes, why?

May 09, 2017 at 03:35 PM


avatar image

we are using SQL Anywhere 11 for Mobilink Synchronization. Some deletes appear and are replicated to the consolidated DB. Some don't appear. It looks like the type 1 deletes are replicated but type 2 deletes are not replicated. Local DB is SQL Anywhere running on Windows Mobile. Consolidated DB is DB2. Mobilink Synchronization logs shows the type 1 deletes in the counts. It does not see the type 2 deletes. Is there any documentation that explains this behavior?

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Chris Keating
Oct 30, 2017 at 12:58 PM

A delete is a delete in UltraLite and SQL Anywhere and should be sent as part of the sychronization (assuming it is part of the publication being sync'd). What exactly do be mean by "type 1" and "type 2" deletes - these are not terminology that SQL Anywhere or UltraLite uses.

An application can use STOP SYNCHRONIZATION DELETE to prevent rows that are deleted from participating in synchronization.

10 |10000 characters needed characters left characters exceeded