The maximum number of seconds between transaction log scans.
60
An integer from 5 to 86400.
The value of the scan_sleep_max parameter is the maximum number of seconds that can occur before the Log Reader component checks the transaction log in the primary database for a transaction to be replicated after a previous scan yields no such transaction.
For shorter replication latency in an infrequently updated database, Sybase recommends lower number settings for the scan_sleep_max parameter.
If the database is continuously being updated, the value of the scan_sleep_max parameter is not significant to Replication Agent performance.