Lab accepting new cases ·  Mon–Fri, 9am–5:30pm Urgent? Call 01273 964902
BDR Brighton Data Recovery 01273 964902 Start a case
BDR / Trickier jobs / Database recovery

Specialist · database recovery

Database recovery, Brighton. Getting the file back is half the job. Making the engine accept it is the other.

If you cannot successfully attach your database, it has not been recovered, only retrieved. Both Microsoft SQL Server and Microsoft Exchange databases have strict internal integrity, and when using their own built-in 'repair' options they discard your data to make the errors go away. In all our database recoveries our procedure is always consistent: we create forensic level copies of each file in your original database first and perform all database repair operations against these copies, never the original files. Brighton database cases start at £500 + VAT (Value Added Tax) and take three to four working days for completion. Priority service is also available.

Only pay if we recover your data, on most jobs Free diagnosis & written quote Post-in from anywhere in Sussex

Talk it through with an engineer
01273 964902

What you're seeing, decoded.

Something else? Run the triage →
The problem as describedWhat it meansFirst thing we do
SQL database marked SuspectThe log could not replay properly due to an unclean shut-downCopy MDF+LDF before anything
Your Recovery Pending operation has stalled and will never finishDatabase startup recovery process stopped: often a hardware failure within the disk subsystemLook to lower layers of the stack as well
Errors 823 / 824 / torn page errorsThe database engine found corrupted pages upon reading themStop retrying and image
Not a primary database file (Error 5171)Damage to the header section of the MDFRepairing the header section of the copied MDF
Exchange: Dirty Shutdown stateTransaction logs were not fully replayed into the EDBHeader check first, gently
Emergency repair has been performed previously on this databaseREPAIR_ALLOW_DATA_LOSS does exactly what it saysGet your quote first, then send us the damaged database anyway. Honestly.
Getting it to us from Brighton: get a quote first by phone or with the form. And we will walk you through packing it. Then post your device tracked and fully insured to our intake laboratory at Guildford (free return postage), or drop it off there Monday to Friday, 9am to 5:30pm (no appointment needed). Details for sending are located on the contact details page.

The rules that keep database recovery honest.

Copies before commandsWe create read-only forensic copies of all logs, LDF, NDF, MDF and EDB files before allowing any tools to operate. Database engines are very aggressive in writing during 'repair', and the copy is what allows us to reverse every single action we take afterwards.
The repair switch that deletesSQL's REPAIR_ALLOW_DATA_LOSS has an unusually honest name: it accomplishes consistency through eliminating everything it cannot reconcile. We rarely run REPAIR_ALLOW_DATA_LOSS, and if we do, it is only on a copy, never as our first line of defence.
Exchange's gentle question firstA built-in check will scan an EDB’s header for its shutdown state, required log range and damage level without altering one single byte of it. The nasty cousin of that check, the hard repair, erases all unreadable pages and compels the migration process to occur. Always diagnose prior to doing surgery.
The storage truth beneathMost 'corrupted databases' are just a storage problem dressed up as a database problem: a dropped RAID member, a sudden loss of power during a flush operation, or a bad snapshot. Therefore we have to take care of the floor (storage) before we worry about fixing the furniture (the database), which is why this page and our server page sit next to each other.

How we recover a database, stage by stage.

01

Booked in, diagnosed free Free

Your device is logged under its own case reference as soon as it arrives. An engineer assesses the fault and confirms what is actually recoverable. And you receive a fixed price in writing: no diagnosis fee. No obligation. And no paid work until you say go.

Free diagnosisFixed written quoteNothing to sign
02

Forensic copies of everything

All of your data files, log files and backup files are image copied in read-only mode, even from failed storage systems; in those cases the playbooks for both the server and RAID processes need to be followed first so that clean source images can be created.

Read-only copiesStorage layer stabilised
03

Recover at engine level

In the copy: headers restored, logs replayed whenever possible and, when that isn’t possible, data pulled out of the internal pages of the file (tables, mailboxes, attachments etc.) using specialised tools.

Logs replayed if usablePage-level extraction if not
04

Prove consistency, then hand over

The resulting file(s) are then put into a state where the engine will accept them (attached, mounted, queried) and validated against what you said was important before anything is considered complete.

Engine-verified resultChecked against your priorities
05

Verified, returned, signed off

You approve a full listing of everything that came back before you pay the recovery fee. Your data returns on new media with free return postage. And the case only closes once you have confirmed all items open on your side.

File listing approvalNew media includedFree return postage

What the lab checks first

  • Suspect is a verdict on the log, not the data: if the engine won’t make guesses regarding recovery, it means the system is working properly; normally the data itself is still good.
  • Error numbers are coordinates: every error number such as 823, 824, 5171 and others refers to a particular data structure. When you bring us the actual error number(s) you receive, the diagnosis will begin before the parcel arrives.
  • Torn pages tell on the hardware: database storage problems frequently cause some form of checksum failure before they begin to produce other symptoms.
  • Backups get imaged too: the 'corrupted' backup that saved a case, and the good backup that someone was almost able to restore over the evidence, are both regular visitors here.

The distinction this whole page turns on: file recovery is complete once we have restored your bytes; DB recovery is complete once the engine attaches, mounts and answers queries. This space between the two end points is where consistency resides, and that's why a recovered MDF from a generic lab frequently shows up here next, still refusing to attach.

From the casebook.

EX · BDR-2026-0851CHECKED ✓

A Sussex practice's SQL database, Suspect at 8:55am

A power outage occurred overnight, and by morning the database was marked Suspect, with an IT contractor's finger poised over the emergency repair button. The forensic copies made first told a better story: the log was intact and able to be played back. Once recovered on the copy, the database attached cleanly, and the morning's appointments ran twenty minutes behind schedule rather than a full week.

Attached clean24 hrs in lab

Before your database files reach us.

Do

  • Shut down the database and make an image of the MDF, LDF and all logs
  • Identify the specific error codes and messages
  • Preserve all existing backups regardless of age or credibility
  • Tell us what application is running on top of the database

Don't

  • Initiate a REPAIR_ALLOW_DATA_LOSS process first
  • Use a hard repair on an Exchange EDB to correct any errors
  • Try repeatedly detaching from the database and then attaching again
  • Restore a previous version of a database from backup over the corrupted version

Asked on this bench, answered honestly.

My SQL database is Suspect — what should I do first?

Not creative: pull it offline and make secure copies of both the MDF (the data file) and LDF (log file) before any tool runs. Suspect usually means the SQL Server Database Engine could not properly read through its own transaction log after an unclean shutdown, which is frequently very recoverable. Most of the time that it becomes unrecoverable, it is due to well-meant repairs done using a SQL Server utility on the original database.

Can you recover a database without its transaction log?

Yes, often. The data contained within the .mdf file contains the actual information, and it is usually possible to get this into a state such that it can be attached without needing the .ldf file. However, one honest price paid here is that if you were in the process of executing transactions when the failure occurred, those transactions in progress at the time of failure could potentially be incomplete. We will inform you specifically about what portion of your transactional activity falls into this category.

Exchange says Dirty Shutdown — is the mail gone?

Most likely not. A Dirty Shutdown means there were outstanding logs that were not played back into the database. The gentle header check names which ones, and soft recovery attempts to play them back where they exist. The mail should still be present; however, using a hard-repair command is what risks losing it.

The corruption keeps coming back after repairs — why?

The reason why recurring corruption happens is because of the fact that the database itself is not the issue; instead it is the underlying disk storage. Almost all cases of recurring corruption occur due to a bad disk, a poorly functioning RAID array or a caching system that writes new corruption into each subsequent 'fix'. This would be considered a server recovery issue that presents itself through a database symptom, and we treat it as both.

Whatever's failed, don't power it on again.

Each time a damaged device starts up again, data is lost. Open a case first; the diagnosis is free either way.

01273 964902