Each MobiLink remote database can contain a different subset of the data in the consolidated database. Stated another way, you can write your scripts so that data is partitioned among remote databases.
The partitioning may be disjoint, or it may contain overlaps. For example, if each employee has their own set of customers, with no shared customers, the partitioning would be disjoint. If there are shared customers, who appear in more than one remote database, the partitioning contains overlaps.
Partitioning is implemented in the download_cursor and download_delete_cursor scripts for the table, which define the rows to be downloaded to the remote database. Each of these scripts takes a MobiLink user name as a parameter parameter. By defining your scripts using this parameter in the WHERE clause, each user gets the appropriate rows.
Disjoint partitioning
Partitioning with overlaps
Partitioning child tables
SQL Anywhere Studio 9.0.2
Copyright © 1989–2004 Sybase, Inc. Portions copyright © 2001–2004 iAnywhere Solutions, Inc. All rights reserved.