Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.

SAP Sybase SQL Anywhere 16.0 » MobiLink - Getting Started » MobiLink tutorials » Tutorial: Using MobiLink with an Oracle Database 10g


Lesson 11: Viewing the data in the remote database

After successfully synchronizing the remote client to the consolidated database through the MobiLink server, the remote database should be populated with information relevant to one salesperson. You can verify that the database is populated correctly in Sybase Central using the SQL Anywhere 16 plug-in.


This lesson assumes you have completed all preceding lessons. See Lesson 1: Designing the schemas.

This lesson assumes you have the roles and privileges listed in the Permissions and privileges section at the start of this tutorial: Tutorial: Using MobiLink with an Oracle Database 10g.

  1. Start Sybase Central.

  2. Connect to the remote database:

    1. In the left pane, right-click SQL Anywhere 16, and click Connect.

    2. In the Authentication dropdown list, click Database, and type DBA as the User ID and sql as the Password.

    3. In the Action dropdown list, click Connect to a running database on this computer. Type remote_eng as the Server name and remote_db as the Database name.

    4. Click Connect.

  3. In the left pane of Sybase Central under remote_db - DBA, expand Tables, click the ORDERS table, and then click the Data tab in the right pane.

    In the ORDERS tables, all the records are for the salesperson with an identifier of 154. This particular salesperson is not concerned with the sales information of other salespeople. For this reason, you set the synchronization scripts to filter out rows by the remote ID, and you set this database's remote ID to the value of a particular salesperson identifier. Now this particular salesperson's database takes up less space, and requires less time to synchronize. Since the remote database size is kept to a minimum, frequently performed operations, such as entering a new sale or processing a refund on a previous sale, run faster and more efficiently.


The remote database is populated only with information relevant to the salesperson with an identifier of 154.


Proceed to Cleaning up.