A database that's dropped into Suspect mode, won't attach, or is throwing corruption errors can stop a business dead — and restoring last night's backup only works if the backup is good. Most corrupt databases can be recovered directly from their data files. We recover SQL Server, MySQL, Oracle, PostgreSQL and every other engine for organisations across Belfast and Northern Ireland, in-house.
$ bdr diagnose /dev/db → Database: SQL Server · MDF · 220 GB → Status: SUSPECT — log damaged, will not mount → Client: confidential · Belfast $ bdr engineer-working → MDF + LDF: copied read-only → Pages: repaired · checksums fixed → Database: online · tables intact $ bdr verify → ✓ tables — 220 GB → ✓ records — all back → ✓ database recovered — data back
When a database is corrupt, the tempting fixes are the dangerous ones: an emergency repair that allows data loss, or restoring a backup straight over the live files. Both can discard recoverable rows for good. Take a copy of the data files as they are — MDF, NDF and LDF, or their equivalents — before running anything, and let us work from that copy.
Databases fail through their data files, their logs, their backups and the storage beneath them. These are the situations we recover most.
We recover every database engine and file type, whether the files are corrupt or the storage beneath them has failed.
Microsoft SQL Server and Access, MySQL and MariaDB, PostgreSQL, Oracle, Exchange, SQLite, MongoDB, Firebird, Sybase and IBM Db2 — covering MDF/NDF/LDF sets, InnoDB and MyISAM (ibdata1 and .ibd), EDB, DBF, ACCDB and BAK — whether they live on a single drive, a RAID set, a NAS or a SAN.
Database recovery works from the files up. We take a copy of the data and log files as they are, repair or extract from that copy, and rebuild a consistent, usable database — and where the storage beneath has failed, we rebuild that first. The originals are never repaired in place.
We identify the engine, the file set and the corruption, and check whether the storage beneath is healthy — then send a written quote.
Where the drive, RAID or array holding the database has failed, we rebuild it from read-only images before touching the database files.
We work on copies of the data and log files — MDF, NDF, LDF or their equivalents — so your originals are never altered by the recovery.
We repair the file structure, pages and indexes, or where repair isn't possible, extract the tables, rows and objects directly from the data file.
We reassemble a consistent, attachable database — recovering from the data file alone where the log is missing — and recover dropped tables and deleted rows.
The recovered database is checked for consistency and that its tables and records are intact, and we can show you what's come back before anything is returned.
Your database comes back as attachable files or an export, on fresh media or via secure transfer — whichever suits your environment.
From a SQL Server database in Suspect mode to a corrupt MDF, a dropped table or a database lost when its RAID failed, we recover every engine — working from copies of the data files, and rebuilding the storage beneath where we have to.
Give us a few details about what went wrong and an engineer will come back to you, usually inside one working day.
We will get back to you soon. If it is urgent, call 028 9002 0144.
Assessment is free, and you approve a fixed written quote before anything happens. Repairing a corrupt database whose files still read starts at £500 + VAT; if the storage underneath — drive or array — has failed as well, pricing starts at £800 and is quoted individually. Most jobs run no fix, no fee, and any physical disk work carries a 50% deposit for parts and bench time with the balance payable only on success.
A representative selection of database recoveries across different engines and faults — configurations and outcomes shown, customer details kept private.
A crash mid-write had left it unable to recover. We worked from copies of the files, repaired the structure, and brought the database back online intact.
The ibdata and .ibd files were damaged. We extracted the tables directly from the tablespace and rebuilt a working database.
A key table had been dropped and there was no usable log. We recovered from the MDF alone and reconstructed the dropped table's rows.
Several data blocks were corrupt and blocking reads. We repaired the affected blocks and extracted the intact schemas and tables around them.
The ACCDB wouldn't open and repair failed. We recovered the tables, queries and forms from the file and rebuilt a working database.
The array under the database had dropped offline. We rebuilt the RAID 5 from images, recovered the MDF and LDF, and brought the database back.
Post or drop in your device for a free diagnostic, with a note on what happened — an engineer reviews it and confirms your exact quote in writing before any work begins.
First step: get the device onto our Belfast bench. Wrap it well, tuck your contact details in the box, and post it over — the diagnostic costs nothing, and you’ll have a firm written price to approve before we touch a single sector.
Posting it? A tracked, insured service is best. Dropping it off instead? You’re welcome Monday–Friday, 9am–5:30pm — please still pack the device as above.
Not ready to send anything yet? Use the form to describe the fault in your own words and one of the engineers will come back with a quote tailored to your situation.
We will get back to you soon. If it is urgent, call 028 9002 0144.
The questions we're asked most about database recovery.
Usually, yes. Suspect mode normally means a log or file problem stopped the database recovering, not that the data is gone. We work from copies of the files, repair the structure or extract the data, and bring the database back online. Take a copy of the MDF, NDF and LDF before running any repair.
Yes — those are among the engines we recover most. Whether the corruption is in the pages, indexes or the file structure, we repair the data file or extract the tables and rows from it directly, and rebuild a consistent, usable database.
Often, yes. Dropped tables and deleted or updated rows usually remain in the data file until they're overwritten. Stop writing to the database as soon as you notice, take a copy of the files, and there's a good chance we can extract the lost records.
Yes — it's a common situation. A missing or corrupt log doesn't mean the data is lost; we recover the database from the MDF or data file alone and rebuild the consistency needed to bring it back online.
For a corrupt database with readable files, work starts at £500 + VAT. When the underlying drive or array has died too, jobs start from £800 and are priced case by case once the free assessment is done. No fix, no fee holds on most jobs, and any physical disk repair takes a deposit for parts and bench hours, the rest due only on success.
On most jobs, yes — no recovery, no fee. Where disks beneath the database need physical repair, a deposit covers those parts and the bench time; the balance is still only charged on success. We're clear about which applies before any work begins.
All the major engines — SQL Server, MySQL, MariaDB, Oracle, PostgreSQL, Microsoft Access, Exchange, MongoDB, SQLite, Db2, Firebird and Sybase — across their data, log and backup files, on any storage.
Yes. When the storage beneath a database fails, we rebuild that first — imaging the disks and reconstructing the array — then recover the database files from it and repair them. It's the same work, one layer down.
Within honest limits, yes. We recover backups, snapshots and any unencrypted copies of the database, and we'll always look for those first. But database files the ransomware has actually encrypted generally can't be decrypted without the key, and we'd never advise paying a ransom.
A readable but corrupt database is often recovered in 2 to 5 working days; where the underlying storage has to be rebuilt first, it typically takes 5 to 10. The assessment is usually finished within a couple of days, and we can prioritise business-critical databases.
If you can copy the files, a secure transfer of the data, log and any backup files is often quickest — get in touch and we'll arrange it. If the database is stuck on a failed drive or array, deliver or post the disks to our Belfast office, fully insured. We're open Monday to Friday, 9am to 5:30pm.
A free assessment, fixed written pricing from £500 + VAT, and no fix no fee on most jobs — every database engine recovered in-house, right here in Belfast. Don't run a lossy repair or restore over the originals — copy the files and send them in.