The remote database needs to be created and configured in order to send and receive messages and participate in a SQL Remote setup. Like the consolidated database, the remote database needs a publisher (in this case, the field_user user ID) to identify the source of outgoing messages, and it needs to have hq_user identified as a remote user. It needs the pub_news publication to be created and needs a subscription created for the hq_user user ID. The remote database also needs to be synchronized with the consolidated database; that is, it needs to have a current copy of the data in order for the replication to start. In this case, there is no data in the table as yet.
The database extraction utility enables you to carry out all the steps needed to create a remote database complete with subscriptions and required user IDs.
To extract a database from the consolidated database for remote user field_user:
In a proper SQL Remote setup, the remote database field would need to be loaded on to the computer using it, together with a SQL Anywhere engine and any client applications required. For this tutorial, we leave the database where it is and use ISQL to input and replicate data.
You should connect to the field.db database as DBA and confirm that all the database objects are created.
The system is now ready for replication. For the next step, inserting and replicating data, see the section "Start replicating data".