- Selection of tables to recover.
- Output of recovered data for each table into separate files.
Saturday, June 24, 2006
As you can see from this forum thread some of ApexSQL Log (aka axLog) users are having performance problems with recovery of large dbs from detached (and in this case seemingly corrupted) MDF files. In this case it's a db with 220gb of data split in 4 files. In the current version of axLog (2005.02, which is comming out tomorrow) recovery process makes one pass through MDF files per recovered table. On the other hand we don't offer selection of tables to be recovered. Put these two things together and you get performance problems on very large dbs. We have been aware of this for a while so in next major version we will offer: