The remote ID is created as a GUID, but you can change it to a more meaningful name. For both SQL Anywhere and UltraLite databases, the remote ID is stored in the database as a property called ml_remote_id.
For SQL Anywhere clients, see Setting remote IDs.
For UltraLite clients, see UltraLite ml_remote_id option.
When deploying a starter database to multiple locations, it is safest to deploy databases that have a NULL remote ID. If you have synchronized the databases to pre-populate them, you can set the remote ID back to NULL before deployment. This method ensures that the remote ID will be unique because the first time the remote database synchronizes, a unique remote ID is assigned. Alternatively, the remote ID can be set as a remote setup step, but it must be unique.
To simplify administrative duties when defining a MobiLink setup where you have one user per remote, you might want to use the same number for all three MobiLink identifiers on each remote database. For example, in a SQL Anywhere remote database you can set them as follows:
-- Set the MobiLink user name: CREATE SYNCHRONIZATION USER "1" ... ; -- Set the partition number for DEFAULT GLOBAL AUTOINCREMENT: SET OPTION PUBLIC.GLOBAL_DATABASE_ID = '1'; -- Set the MobiLink remote ID: SET OPTION PUBLIC.ml_remote_id = '1';