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

SQL Anywhere 12.0.1 » MobiLink - Getting Started » MobiLink tutorials » Tutorial: Using MobiLink with an Adaptive Server Enterprise consolidated database


Lesson 11: Viewing the data in the remote database

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

After successfully synchronizing the remote client to the consolidated database through the MobiLink server, the remote data should be populated with information relevant to one store. You can verify the contents of the remote database in Sybase Central using the SQL Anywhere 12 plug-in.

 View the data in the remote database
  1. Start Sybase Central.

  2. Connect to the remote database:

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

    2. In the Authentication dropdown list, choose Database, and perform the following steps:

      1. In the User ID field, type DBA.

      2. In the Password field, type sql.

    3. From the Action dropdown list, choose Connect To A Running Database On This Computer.

    4. In the Server Name field, type remote_eng and in the Database Name field, type remote_db.

    5. Click Connect.

  3. If the tables created from the consolidated database are not visible, perform the following steps:

    1. Right-click remote_db, and Configure Owner Filter.

    2. Choose dbo, and click OK.

      The tables created from the consolidated database appear in the left pane. Ownership of these tables by dbo is preserved in the remote database.

  4. Choose any remote table, and click the Data tab in the right pane.

    In the sales, salesdetail, and stores tables, all the records are for the store with an identifier of 5023. This particular store is not concerned with the sales information of other stores. 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 store identifier. Now this particular store'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.

  5. Proceed to Cleaning up.