A corrupt database, a SQL Server stuck in Suspect mode, a dropped table, or a lost transaction log? We recover SQL Server, MySQL, Oracle and every other engine — repairing the database at page level, rebuilding it from the data file where needed, and extracting your tables and records, all from copies and never your originals.
$ bdr diagnose /dev/db → Database: SQL Server · MDF · 220 GB → Status: SUSPECT — log damaged, will not mount → Client: confidential · Wallsend NE1 3DY $ 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
If your database is corrupt, sitting in Suspect mode or refusing to mount, stop — don’t run repair commands that permit data loss, restore over it, or carry on writing to it. Any of those can overwrite the very data we’re trying to recover. Take the database offline, leave the data and log files exactly as they are, and call us. The first attempt is always the safest, and we work only from copies.
From a corrupt MDF to a dropped table, these are the database failures we recover from most — corruption, suspect mode, deletion and storage.
We take on every database — SQL Server, MySQL, Oracle, PostgreSQL, Access and the rest — corrupt files, dropped tables, lost logs, failed restores. The engine sets the method; it doesn’t decide whether we can help.
Microsoft SQL Server (MDF, NDF, LDF), MySQL and MariaDB (InnoDB, MyISAM), Oracle (DBF), PostgreSQL, Microsoft Access (ACCDB, MDB), Exchange (EDB), MongoDB and SQLite · corrupt files, suspect databases, dropped tables, lost logs and failed backups · on any drive, RAID, NAS, SAN or server.
Database recovery means getting your data out of a database the engine can no longer open. We work from a copy of the files, repair the database at page level — or rebuild it from the data file alone — and extract your tables, records and schema, recovering the storage underneath first if that’s failed.
Tell us the database — engine and version, the files you have, what happened. We assess it and send a written quote, usually inside 48 hours.
We make a read-only copy of the database files — MDF, NDF, LDF, IBD, DBF or EDB — and if the drive or array has failed, we recover that first, so the originals are never written to.
Where the drive, RAID or server holding the database has failed, we repair and image it, or rebuild the array, before any database work. Drive-level repairs need 50% of the fee upfront.
We repair the database at page level — fixing corrupt pages, checksums and headers — and where the log’s missing, rebuild a consistent database from the data file alone.
We extract your tables, records, schema and stored procedures — to a working database, scripts or CSV — pulling the most complete and consistent copy of the data.
We check the recovered tables and records are readable and consistent — row counts, key data and structure — before any of it comes back to you.
We return your recovered database ready to attach, or your data as exports, whichever suits how you need to put it back into service.
Every database — SQL Server, MySQL, Oracle and the others — recovered by repairing corrupt files, rebuilding from the data file alone, and extracting your tables and records, whatever’s happened to the database or its storage.
Tell us what happened and we’ll get back to you, usually within a working day.
We’ll be in touch shortly. If it’s urgent, call 0191 406 1051.
Clear, tiered pricing for database recovery — with a free diagnostic and a quote in writing before any work starts.
A handful of recent database recoveries across corrupt files, suspect databases, dropped tables and failed storage. Identifying details removed, every result verified.
A damaged log was keeping the database offline. We repaired both the data and the log, and brought every table back.
MySQL wouldn’t start — the ibdata file was damaged. We rebuilt the tablespace and got every database back.
The rows were still sitting in the data file. We carved the dropped table back out and recovered every record.
A run of blocks had gone unreadable. We mended the datafile and pulled the schema and data out intact.
A damaged file header was the whole problem. We rebuilt the database and recovered every table and form.
Two disks had failed beneath the database. We rebuilt the array first, then repaired and recovered the database sitting on it.
Real client stories from our two-decade testimonial archive.
We had a Qnap Raid 5 eight disk system. Two of the hard disk failed, we replaced disks and attempted a rebuild. After rebuild completed system would not start. We had business critical accounts, SQL Database and Exchange Database on Qnap server. Newcastle Data Recovery provided us with reassurance from the start that they could recover the data. They got the system in on Thursday and we downloaded the SQL and Exchange files from them on Sunday afternoon so all staff could work as normal on Monday. 1st class customer service.
Send the device in for its free diagnostic and tell us briefly what happened; an engineer reviews it and confirms your exact quote in writing before anything starts.
Getting your data back begins with getting the device to us. Pack it up safely, pop your contact details inside, and send it over — once we’ve run the free diagnostic, we’ll confirm your exact price in writing before any work starts.
Posting it? A tracked, insured service is what we’d recommend. Rather drop it in? You’re welcome Monday to Friday, 9am to 5:30pm — just package the device up as above first.
Want a bit more detail first? Fill in the form with more about your issue and an engineer will review it and send you a custom quote.
We’ll be in touch shortly. If it’s urgent, call 0191 406 1051.
The things people most often ask us about recovering a database.
Usually, yes. Suspect mode normally means a problem with the transaction log or a data file, not that the data’s lost. We work from a copy, repair the data and log at page level, and bring the database back online with its tables intact. Don’t run repair commands that allow data loss first — ask us.
Yes. We repair database files at the page level — corrupt pages, checksums, headers and indexes — for SQL Server, MySQL, MariaDB, Oracle, PostgreSQL and more, then extract your tables, records and schema, even when the engine can’t open the file.
Usually, yes, if you act quickly. Dropped tables and deleted rows normally stay in the data file or transaction log until they’re overwritten. Stop writing to the database and contact us — we carve the data back out and recover the records, the sooner the better.
Usually, yes. When the transaction log’s missing or corrupt, we can rebuild a consistent database from the data file alone — MDF, IBD or DBF — and recover the tables inside, so a lost LDF doesn’t mean a lost database.
Repairing a corrupt database whose files are readable starts at £500 + VAT. Where the drive, RAID or server holding the database has also failed, recovery starts at £800 + VAT, depending on the storage and the work involved. Every job opens with a free diagnostic and a written quote, and most are no fix, no fee.
On most jobs, yes. Where drive-level repairs are needed we take a 50% deposit upfront and the rest is only due if we recover your data — so if we can’t, you’re not left with the full bill.
Every engine — Microsoft SQL Server, MySQL, MariaDB, Oracle, PostgreSQL, Microsoft Access, Exchange, MongoDB, SQLite and more. The engine decides the method, not whether the data can be recovered.
Yes. Where the drive, RAID, NAS or SAN holding the database has failed, we recover the storage first — imaging the drive or rebuilding the array — then repair and recover the database on it. The storage layer and the database are both things we handle.
Sometimes. Databases are a common ransomware target, and where there are unencrypted pages, earlier copies or backups left, we can often recover the data. A fully encrypted database needs special handling, so ask us about that separately — and don’t pay anything before you do.
A readable database is usually repaired in 2 to 4 working days. Where the storage beneath it has failed as well, allow 4 to 7. The free diagnostic normally lands inside 48 hours, and pressing business jobs can often be moved up the queue.
If the storage’s healthy you can send the database files on a drive, or drop them at our Newcastle location Monday to Friday, 9am to 5:30pm, or post them fully insured. If the drive or array has failed, send the disks labelled with their bay order. Include your name, company, address, phone number and email so we can book it in and quote before any work begins.
A free diagnostic, tiered pricing from £500, and no fix no fee on most jobs — every database recovered, SQL Server, MySQL, Oracle and the rest, file and storage. Begin your recovery today.