Creating synchronization models

Set up a MobiLink application with the Create Synchronization Model Wizard

Use the MobiLink plug-in to create a MobiLink project for your consolidated database if you have not already created one.

See Creating a MobiLink project.
In the left pane of Sybase Central, expand your MobiLink project name, and then click Synchronization Models.
From the File menu, choose New » Synchronization Model to start the Create Synchronization Model Wizard.
From the Welcome page, choose a name for your synchronization model. Your model is stored as a .mlsm file in the project directory. Click Next.
On the Primary Key Requirements page, select the three checkboxes and then click Next. For more information about primary keys, see Maintaining unique primary keys.
On the Consolidated Database Schema page, select the consolidated database for obtaining your consolidated database schema from the list, and then click Next. the schema from the consolidated database is loaded.

If you chose an Oracle database, you may be prompted to choose a subset of owners because loading schema for all owners can take a long time.
The Remote Database Schema page appears. You can create your remote database schema based on the consolidated database schema or an existing remote database. The existing remote database can be SQL Anywhere or UltraLite. For help deciding, see Remote schemas.
Follow the remaining instructions in the Create Synchronization Model Wizard. Default recommendations based on best practices are used where possible.
Click Finish.

When you click Finish the synchronization model is opened in the left pane of Sybase Central. You are now working offline and you can make changes to the model. No changes are made outside the model until you deploy the model: the consolidated database does not change and the remote database is not created or changed until that time. See Synchronization model tasks and Deploying synchronization models.

Remote schemas

A synchronization model contains schema for a remote database. This schema can be obtained from an existing remote database or from the consolidated database.

Use an existing remote database in the following cases:

If you already have a remote database, especially if its schema is not a subset of the consolidated database schema.
If your consolidated and remote columns need to have different types.
If your remote tables need to have different owners from the tables on the consolidated database. For a new SQL Anywhere remote schemas created from the consolidate database, the owner of the remote tables is the same as the owner of the corresponding consolidated database tables. If you want a different owner, you should use an existing SQL Anywhere remote database with table ownership you set up.

Tip

You can manually change an existing database schema and then run the Update Schema Wizard to update the synchronization model in your MobiLink project. See Updating schemas.

When you deploy your model, you have three options for your remote database, regardless of how you created the remote schema in the model. Your deploy-time options for the remote database are:

Create a New Remote Database Deployment can create a new remote database using the remote schema from the synchronization model. the database is created with default options.
Update an Existing Remote Database That Has No User Tables If you deploy to an empty remote database, then the remote schema from the model is created in the database. This option is useful when you want to use non-default database creation options, such as collation.
For SQL Anywhere databases, you can see a list of options that cannot be set after the database is created in the Remarks section of the initialization utility. See Initialization utility (dbinit).

For UltraLite databases, database properties cannot be changed after the database is created. See Choosing database creation parameters for UltraLite.
Update an Existing Remote Database That Has a Schema Matching the Schema in the Model This option is useful when you have an existing remote database that you want to synchronize. When you deploy directly to an existing remote database, no changes are made to any existing remote data. If you try to deploy directly to an existing remote database whose schema doesn't match the remote schema in the model, you are prompted to update the remote schema in the model.

For a SQL Anywhere remote database, tables have the same owners as the original database. UltraLite database tables do not have owners.

Creating synchronization models

Set up a MobiLink application with the Create Synchronization Model Wizard

Remote schemas

Tip

See also