We have many Microsoft SQL Server end points. Due to the way our SQL backups are configured, we have the Change processing mode (read changes from): set with the Online Logs only. What we have found, and confirmed with Qlik support, is that when Replicate can not find the needed LSN it will move forward to the first available LSN. There is no warning nor error message in the logs when this happens. Therefore, we miss processing of source transactions with no awareness of the loss.
When the option is set to Prioritize Online Logs the tool will provide an error that the needed LSN can not be found. We find this discrepancy in behavior to be unacceptable. A replication tool should never skip data without an error. We would like to see an option to error out when Online Logs Only is selected and a needed LSN is not available.
