It is very inefficient to create a large number of remote databases by running the Extraction utility for each one. You can make the process much more efficient. This section describes one way of making the process more efficient.
There are several potential causes of inefficiency in a large-scale extraction process:
Running at isolation level 3 may hamper others' turnaround time on the server because of the large number of locks required. It is recommended that you run the Extraction utility when the server is not busy, or run it against a copy of the database.
One approach that avoids these problems is as follows:
To start several subscriptions within a single transaction, use the REMOTE RESET statement.
This solution interferes with the production database only during the first step. The copy must be made at isolation level three if the database is in use, and uses large numbers of locks. Also, the subscriptions must be started at the same time that the copy is made. Any operations that take place between the copy and the starting of the subscriptions would be lost, and could lead to errors at remote databases.
|Send feedback about this page via email or DocCommentXchange||Copyright © 2008, iAnywhere Solutions, Inc. - SQL Anywhere 11.0.0|