SQL Server marked the database as 'suspect'. Exchange will not mount the store and cannot talk about it. The Access file at the centre of a thirty-year-old company's business displays gibberish when opened. Database recovery is a separate science (pages, logs, consistency), and there is one thing that gives an administrator the best chance to recover their data: never use the 'repair' command until they know how it will affect their data.
Databases die in two ways. First, under them: when the drive or array that contains the MDF, EDB, or DBF files fails, which is a storage recovery first, then database validation second. This is because a database that has been recovered 99.9% intact can still refuse to be mounted based on the 0.1% that was missed. Second, inside them: when there is corruption in the page structures themselves (torn pages due to power loss, checksum failures, indexes that point nowhere), where the files are perfectly readable but perfectly broken. The bench handles both: page-level repair and record extraction for structural damage, and transaction-log work (redo, replay, rescue of the log itself) where the LDF holds the missing history.
The most damaging tools available to help you recover your databases are built into your database software packages: these include commands (like SQL Server's repair_allow_data_loss) that allow you to 'fix' consistency issues by eliminating any records that fail validation, commands administered by an administrator who may be under pressure and may only have access to one copy. One house rule we follow, and one that should also become yours: do not let any tool or script execute against your original files. Shut down the server if you can and make a copy of the original database and log files somewhere untouched, if you safely can; then document the history of the database, including its version number, what occurred and what the last known-good backup is. If your storage media has failed, send us the individual disks labelled by the bay where they reside, rather than sending us the entire server. We'll work on bench copies of the recovered database, preserve any salvaged records, and document which (if any) records were truly lost.
Not yet: the aggressive repair modes permanently delete what they can’t validate. These are the largest cause of avoidable database loss we see. Before making any repair decisions, always make a copy of your MDF and LDF files or image the volume on which those files reside, so those decisions can be made on copies where mistakes cost nothing.
Mostly: dirty-shutdown states and EDB corruption usually respond to log replay and store-level repair on copies. Even if the entire store won’t remount, individual mailboxes can be extracted. Keep all logs as well as the EDB, as the logs are frequently the recovery.
No, legacy formats are well-known territory for us, and in many cases corrupted Access databases have a problem that is shallower than it looks, such as damaged headers or index files that don't damage much of your good data. The tables and all the other data can be extracted into an uncorrupted database (a clean file) or you can choose a newer format. First get a quote, either by phone or using our form. Then just send the damaged file(s), along with their backup(s), no matter how old they may be.
First, a free diagnostic, then a fixed written quote before any work is done. This means no surprises on the invoice (because we don't give you an invoice until you approve the number).
It will take only two moves to place your device at our service area, and once that has been accomplished, the clock on your free look starts.
First get a quote, over the telephone or using the online quotation form. When sending your internal drive, remove all cables, caddies and power supplies, as they will have little use when sent to us. But when sending an external drive, send the complete item, including its original casing, together with the supplied cable and power supply. Ensure that the device is securely wrapped and unable to move during transportation. Either post it insured to 4 Redheughs Rigg Westpoint, South Gyle, Edinburgh EH12 9DQ or call into our offices Monday to Friday, 9am to 5:30pm, with no appointment needed. Please include a brief description of how your device was damaged. If you have printed a shipping form, please attach it along with the device.
Once the arrival of your device has been confirmed, the diagnostic will run free of charge, and then when we make the phone call to you, we'll name the problem and tell you the fixed price to fix it. The bench will remain dormant on your device until you give us permission to proceed.
First, a free diagnostic. We image the underlying storage before doing any database-level repairs. Therefore, if a repair attempt goes wrong, it cannot become a second disaster.