Choose your SQL Anywhere consolidated database or create a new SQL Anywhere database. The remote databases, which are also SQL Anywhere databases, are created from the consolidated database.

When creating a new SQL Anywhere database, consider how SQL Remote uses primary keys. For example, a good practice is to choose BIGINT with global autoincrement for the primary key column data type. See Duplicate primary key errors.

Determine what data to replicate.

When creating an efficient replication system, you decide on the tables that you want to use, the columns from those tables, and finally the subset of rows to replicate. Only include the information that is needed.

Create publications on the consolidated database.

SQL Remote uses a publish and subscribe model to ensure that the correct information reaches its intended user. Arrange the data that you want to replicate into publications on the consolidated database. See Publications and articles.

Create a publisher user on the consolidated database.

A publisher is a user with PUBLISH authority and the publisher is used to uniquely identify the consolidated database. See PUBLISH permission.

Create the remote user.

A remote user is used to uniquely identify a remote database. See REMOTE permission.

When you create a remote user, you define the message type to use when transporting the data and, optionally, you define how frequently to send the data.

Subscribe the remote users to publications by creating subscriptions. See Subscriptions.

Determine how the remote users can use the data.

Remote users can always read their data. You can also allow them to update, delete, and insert data. See Understanding transaction log-based replication.

Choose a method for resolving conflicts.

Conflicts can occur during replication when your remote users update, delete, or insert data. You must implement methods for resolving conflicts. See Default resolution for update conflicts.

Deploy the SQL Remote system.

Create the remote databases and install the appropriate software. See Managing SQL Remote systems.