I have setup my SQL Remote to send every 10 minutes. What happens when it takes more than 10 minutes for DBRemote to run?
Prior to version 5.5, DBRemote starts the waiting period based on the finish time of the prior run. So if DBRemote is set for SEND EVERY 00:10 the 10 minutes is measured from the completion of the previous send cycle, not the start. We do not recommend setting the cycle length very small. Reading the transaction log involves a great deal of disk activity, if the cycle length is too small, too much time is spent reading old transactions instead of replicating new transactions thereby reducing overall performance. As of version 5.5, continuous mode every ten minutes will always run on the hour, ten minutes after the hour, twenty minutes after the hour, etc. If it takes longer that 10 minutes to process the log and then receive new incoming messages, then DBRemote will not wait before processing the log again.
