The remote ID uniquely identifies a remote database in a MobiLink synchronization system. When a SQL Anywhere database is created, the remote ID is null. When the database synchronizes with MobiLink, MobiLink checks for a null remote ID and if it finds one, it assigns a GUID as the remote ID. Once set, the database maintains the same remote ID unless it is manually changed.
If you are going to reference remote IDs in MobiLink event scripts or elsewhere, you may want to change the remote ID to a more meaningful name. To do this, you set the ml_remote_id database option for the remote database. The ml_remote_id option is a user-defined option that is stored in the SYSOPTION system table. You can change it using the SET OPTION statement or using the SQL Anywhere 12 plug-in to Sybase Central.
The remote ID must be unique within your synchronization system.
If you set the remote ID manually and you subsequently recreate the remote database, you must either give the recreated remote database a different name from the old one or use the ml_reset_sync_state stored procedure to reset the state information in the consolidated database for the remote database.
In most cases, you do not need to set the remote ID or know its value. However, in the event that you do need to change it, the safest time to change the remote ID is before the first synchronization. If you change it later, be sure you have performed a complete, successful synchronization just before changing the remote ID. Otherwise you may lose data and put your database into an inconsistent state.
Discuss this page in DocCommentXchange.
|Copyright © 2012, iAnywhere Solutions, Inc. - SQL Anywhere 12.0.1|