How to create and maintain a full chain of transaction log backups

Applies to
ApexSQL Log, ApexSQL Recover

Summary
A tutorial on how to use transaction log “chains” to provide sufficient data sources for successful disaster recovery, transaction rollback or database auditing, effectively avoiding a large singular log file.

How to use ApexSQL Recover after data loss?

Applies to
ApexSQL Recover

Summary
What to do immediately after data loss in order to minimize the chance of the data being overwritten or lost beyond recovery, and therefore maximize recovery success rate.

Description
To recover lost data, ApexSQL Recover reads the database data file (MDF) and transaction log files (LDF). The information about truncated and dropped records can be read only from the MDF files. When a record is dropped, deleted, or truncated, it’s marked for overwriting in the MDF file. It will be overwritten by new database activity, and once that happens, ApexSQL Recover will not be able to recover the lost record. That’s why it is important to prevent overwriting of the MDF file.

How to audit operations for dropped or re-created tables with Old Table ID mapping

Applies to
ApexSQL Log
ApexSQL Recover

Summary
This article describes how to retrieve schemas and objects for the records that are shown as UNKNOWN in the Main grid. This happens when the table with the specific ID doesn’t exist in the database anymore, and the transactions for that object ID exist in the transaction logs used.
This happens when: