Use the consolidated database to complete all SQL Remote administrative tasks. The following is a summary of the steps you need to complete to create a SQL Remote system.
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, keep in mind how SQL Remote uses primary keys (there is the potential for duplicate primary keys when remotes replicate to the consolidated database). A good practice is to choose BIGINT with GLOBAL AUTOINCREMENT for the primary key column data type.
Determine what data to replicate.
To create an efficient replication system, you need to 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.
Create a publisher user on the consolidated database.
A publisher is a user with PUBLISH authority.
Create the remote users on the consolidated database.
A remote user is used to uniquely identify a remote database.
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.
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.
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.
Deploy the SQL Remote system.
Create the remote databases and install the appropriate software.
Publications and articles
Transaction log-based replication
Replication conflicts and errors
Row not found errors
Referential integrity errors
Duplicate primary key errors
Row partitioning among remote databases
Disjoint data partitions
Unique identification numbers for remote databases
Discuss this page in DocCommentXchange.
|Copyright © 2012, iAnywhere Solutions, Inc. - SQL Anywhere 12.0.1|