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

SQL Anywhere 11.0.1 » SQL Remote » SQL Remote Replication Design » SQL Remote introduction

 

Typical SQL Remote setups

SQL Remote is designed for replication systems with the following requirements:

  • Large numbers of remote databases   SQL Remote can support thousands of remote databases in a single installation because the messages for many remote databases can be prepared simultaneously.

  • Occasionally connected   SQL Remote supports databases that are occasionally connected or indirectly connected to the network. SQL Remote is not designed for instantaneous data availability at each site. For example, it may use an SMTP email system to carry the replication.

  • Low to high latency   High latency means a long lag time between data being entered at one database and being replicated to each database in the system. With SQL Remote, replication messages can be sent at intervals of seconds, minutes, hours, or days.

  • Low to moderate volume   As replication messages are delivered occasionally, a high transaction volume at each remote database can lead to a large volume of messages. SQL Remote is best suited to systems with a relatively low volume of replicated data per remote database. At the consolidated database, SQL Remote can prepare messages for multiple databases simultaneously.

  • Homogeneous databases   Each SQL Anywhere database in the system must have a similar schema.


Server-to-remote database replication for mobile workforces
Server-to-server database replication among offices