To solve this issue simply add full transaction log chain when adding transaction logs in "Select data sources" step.
To do so, please consult following article for more info:
Create and maintain the full chain of transaction log backups
Reason that tool occasionally hangs is very much related to a missing full t-log chain.
Additionally, regularly taken transaction log backups must be sequential so tool don't end up performing auditing with gaps in data.
This cause ApexSQL Log to hangs cause it is trying to read something that isn't there at the time.
This is not a bug, it is the expected behavior of the tool.
Please note that only adding full backup is not enough to ensure all the transactions are in them, same goes for reading only online transaction logs.
Regularly taken transaction logs are mandatory so no gaps in data will occur.
© ALL RIGHTS RESERVED. Feedback Nutzungsbedingungen Datenschutz Cookie Preference Center