This is especially important when recovering the UPDATE operations since each UPDATE has at least an INSERT statement as its predecessor, and data history can vary.
Apex sql recovery full#
When an online transaction log file has been truncated, in order to be able to expect the full range of results, it is essential to provide a full chain of transaction log backups, so ApexSQL Recover (and ApexSQL Log as well) can create a historical recovery, and trace the history of the rows.
In case of recovery model being set to simple, the transaction log files will contain only a limited amount of data, and only a small chunk of the most recent operations will be available for auditing/recovery. In order for ApexSQL Recover (and ApexSQL Log as well) to show/recover all transactions for a specific database, the recovery model of the database has to be set on ‘full’.
Apex sql recovery Offline#
With all this in mind, recovery range is limited when working with databases with the simple recovery model.One thing to keep in mind is that it is essential switch the database into the offline mode immediately once the need for recovery is acknowledged in order to try and keep the recover source information in both ldf and mdf as complete as possible. This leaves only the data in the MDF file as a source of information, and this data is also regularly overwritten by the SQL Server, and is hence not reliable and may already be gone. Since the simple recovery model doesn’t guarantee that the information which ApexSQL Recover needs will be available, due to the fact that there are no transaction log entries since SQL Server overwrites information in the ldf to keep the disk space consumption at the minimum.
Full step-by-step guide is available in this article. Recovered data can be added to the new database or in the shape of the SQL Script for easier recovery process. This option enables the user to extract the data and/or structure only for the specific tables, instead of having to restore a full database backup on another location, and to extract from there, saving both time and space. In this case, the Extract from database backup feature should be used for maximum results.