This page allows you to set the method of resolution for detected conflicts.
This page has the following components:
Consolidated database wins Select this option to reject all uploaded updates from the remote database that conflict with the consolidated database.
Remote database wins Select this option to accept all uploaded updates from the remote database, even if they conflict with the consolidated database. You should only use this option with column-based conflict detection. Otherwise, it is the same as not using conflict detection.
Newer wins, using a timestamp column that you maintain Select this option to use a timestamp column to determine which changes should be accepted. This option applies only to tables that have a timestamp column.
Timestamp column Choose the timestamp column from the dropdown list.
This timestamp column must exist and its value must be maintained in both the remote and consolidated database tables. This option may require you to change your applications or use triggers to maintain the value.
Do not choose the same column that is used by timestamp-based downloads. That column records the last time rows were changed on the consolidated database, and it should not be synchronized.
Custom conflict resolution Select this option to use your own resolve_conflicts script. You can write the script in the Model mode Events tab after this wizard finishes. See Resolving conflicts with resolve_conflict scripts.
You can view and modify these options, after the Create Synchronization Wizard finishes, in the Model mode Mappings tab. See Modifying conflict detection and resolution.
|Discuss this page in DocCommentXchange.
Send feedback about this page using email.
|Copyright © 2009, iAnywhere Solutions, Inc. - SQL Anywhere 11.0.1|