Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.
To run the SQL Remote Message Agent (dbremote) in continuous mode, for example on the consolidated database, you must ensure that every REMOTE user either has a send frequency specified. In continuous mode, the SQL Remote Message Agent (dbremote) sends messages at the times specified with the SEND AT or SEND EVERY property.
The SQL Remote Message Agent (dbremote) supports the following send frequency values:
SEND EVERY Specifies a length of time to wait between sending messages.
When any user with SEND EVERY set is sent messages, all users with the same frequency are sent messages at the same time. For example, all remote users who receive updates every twelve hours are sent updates at the same time, rather than being staggered. This reduces the number of times the SQL Anywhere transaction log has to be processed. You should use as few unique frequencies as possible.
A send frequency can be specified in hours, minutes, and seconds in the format HH:MM:SS.
SEND AT Specifies a time of day at which messages are sent.
Updates are sent daily at the specified time. You should use as few distinct times as possible rather than staggering the send times. You should choose times when the database is not busy.
Default setting (no SEND clause) If any user has no SEND AT or SEND EVERY clause specified, the SQL Remote Message Agent (dbremote) runs in batch mode, sending messages every time it is run, and then stopping. See Run the SQL Remote Message Agent (dbremote) in batch mode.
Discuss this page in DocCommentXchange.
|Copyright © 2010, iAnywhere Solutions, Inc. - SQL Anywhere 12.0.0|