Contents Index How SQL Remote handles conflicts A first conflict resolution example

SQL Remote User's Guide
  SQL Remote Design for Adaptive Server Enterprise
    Managing conflicts

Implementing conflict resolution


This section describes what you need to do to implement custom conflict resolution in SQL Remote.

Required objects 

For each table on which you wish to resolve conflicts, you must create three database objects to handle the resolution:

These objects need to exist only in the consolidated database, as that is where conflict resolution occurs. They should not be included in any publications.

Naming the objects 

When a table is marked for replication, using the sp_add_remote_table or sp_modify_remote_table stored procedure, optional parameters specify the names of the conflict resolution objects.

The sp_add_remote_table and sp_modify_remote_table procedures take one compulsory argument, which is the name of the table being marked for replication. It takes three additional arguments, which are the names of the objects used to resolve conflicts. For example, the syntax for sp_add_remote_table is:

exec sp_add_remote_table table_name
   [ , resolve_procedure  ]
   [ , old_row_table ]
   [ , remote_row_table ]

You must create each of the three objects resolve_procedure, old_row_table, and remote_row_table. These three are discussed in turn.

Once these objects are created, you must run the sp_add_remote_table or sp_modify_remote_table procedure to flag them as conflict resolution objects for a table.

Limitations 

Contents Index How SQL Remote handles conflicts A first conflict resolution example