The lab is taking new cases · 9am–5:30pm, Mon–Fri Urgent? Ring 0800 6890668
SDR Southampton Data Recovery 0800 6890668 Open a case
SDR / Harder cases / Recovering databases

Specialist work · databases

Database recovery, Southampton. Retrieving the file is only half of it. The engine has to take it back too.

A database that will not attach was retrieved, but not recovered. Both SQL Server and Microsoft Exchange enforce their own internal consistency, and the repair utilities included within each product win any conflict over data integrity by discarding your data. Therefore, there is no variation on the order of recovery: first, create a forensic image of all files. Then perform engine-level repairs against these images, never against what we received from you.

Only pay if we recover your data, on most jobs Free diagnosis & quote in writing Postal intake across all of Hampshire

Speak to an engineer about it
0800 6890668

What database errors actually mean.

Not listed? Try the fault finder →
The complaintWhat that tells youFirst step
SQL Server database flagged SuspectAfter a dirty shutdown, the log could not be replayed correctlyTake copies of MDF and LDF first
Recovery Pending that simply sits thereStartup recovery has stalled, typically due to a disk problem underneathLook at the storage as well
823, 824 or torn-page errorsThe engine spotted bad pages while reading themHalt the retries and image it
Error 5171: not a primary database fileThe MDF header is damagedRebuild the header on a copy
Exchange sitting in Dirty ShutdownNot all logs made it into the EDBStart with a gentle header read
A hard repair has already been attemptedREPAIR_ALLOW_DATA_LOSS behaved exactly as its name warnsStill worth sending in
Posting it: first, get a price quotation from us, by phone or with the form. Then send your item to us via tracked, fully insured post to our secure intake laboratory where it will be processed (we pay for return postage). Alternatively, you may also bring it to our Guildford intake laboratory Monday to Friday, 9am to 5:30pm, no appointment needed. Ring us and we would be happy to assist you with packaging, and there are postage details available on the postal details webpage.

The database ground rules we will not bend.

Images first, commands laterForensic read-only copies of MDF, NDF, LDF and EDB files, along with every log, are created before any repair tool is pointed at them. Engines write heavily during a 'repair', so it is the copy that keeps each following step reversible.
The switch that throws data awayMicrosoft SQL Server’s REPAIR_ALLOW_DATA_LOSS option has an unusual level of candour regarding its own operation; it achieves consistency through erasure of whatever data it can't be made to agree upon. If we use this option at all, it is only on our copy of the database and only as a last step, never as an opening move.
Ask Exchange politely to begin withA simple self-check is performed using the EDB file’s header without altering one bit from the original: shutdown status, required log ranges and how far the damage goes. The destructive version, a full “hard” repair, will delete any page(s) which can’t be read, followed by forced migration(s). We should always "look" (via checking) prior to attempting to "cut" (via destructive recovery).
The truth lies in the storageMost "database problems" are just a storage error in disguise. A RAID member dropped out, there was an interruption during a flush (the process of writing to disk), or a snapshot failed. We can't fix up the broken chairs while standing on shaky ground. That's why our server recovery page sits next to this one.

How the recovery runs, step by step.

01

Logged in, checked at no cost Free

Your item will have a unique case number assigned to it immediately after we receive it. An engineer will diagnose the issue, tell you what can genuinely be recovered and then provide you with one fixed price in writing. The diagnosis itself is completely at no cost to you. You are under no obligation to allow us to do any work that would incur a charge.

No-cost diagnosisQuote fixed in writingNothing to commit to
02

Everything imaged, read-only

We create a complete read-only copy of all data files, logs, backups and even the failing storage; on those, the server and RAID procedures come first, in order to make sure the source copies we work from are good, clean images of the data.

Copies taken read-onlyUnderlying storage steadied
03

Work done at engine level

Everything we do is with the duplicate copies: the header rebuilds are done and log replays as often as possible. If that can't happen, the inside pages of every file are read directly with a specialist tool to get their tables, mailboxes and attachments.

Usable logs replayedOtherwise, extraction page by page
04

Consistency proved before handover

Once the result has reached a point where the engine genuinely accepts it (attaching, mounting and answering queries), it is checked against the things you told us mattered before anything is signed off.

Result verified by the engineWeighed against your priorities
05

Checked, returned, signed off

Once you have the complete listing of all the recoverable files back from us, you can "sign-off" and your recovery fee becomes due. Once you've signed-off, all the files will be posted out to you on new media (with postage included) and the case will remain open until you confirm that they can be opened properly at your location.

Sign-off on the file listNew media providedReturn postage on us

First checks on the bench

  • Suspect judges the log, not what is stored: when an engine refuses to guess, it is performing exactly as intended, and the data located behind that refusal is normally fine.
  • Each of the errors is a reference to a particular structure (e.g. 823, 824, 5171, etc.): so if you read us the error codes over the phone we can begin working out what went wrong even before your package gets here.
  • A torn page is the disk talking: checksum errors within your database are often the first sign that the storage system underneath it is quietly failing.
  • We also make images of the backups: the "useless" backup that ends up saving the job and the healthy backup someone was about to write over the evidence with are both familiar visitors.

This is the key line that everything else hinges upon: file recovery is complete as soon as the bytes exist again; database recovery is complete once the engine attaches, mounts and answers a query. Consistency resides in the space between those two points, which is why an MDF recovered by a general-purpose lab so often arrives with us afterwards, still refusing to attach.

Out of the casebook.

EX · SDR-2026-0851SIGNED OFF ✓

SQL database at a Hampshire practice, Suspect at 8:55am

Power went down overnight and when the next day came up the database was in "suspect" status and a contract IT guy was getting ready to perform emergency recovery. The forensic copy looked much better: the log file could still be replayed. Recovery was performed on the copy, which attached perfectly, and instead of a week's worth of lost business due to lost data, the booking delays were 20 minutes.

Attached intact24 hrs on the bench

While it's still with you.

Do

  • Stop the database, then copy the MDF, LDF and log files
  • Write down every error number and message exactly as shown
  • Keep every backup, even old or suspect ones
  • Tell us which application runs on top of it

Avoid

  • Reach for REPAIR_ALLOW_DATA_LOSS straight away
  • Throw a hard repair at an Exchange EDB in the hope of fixing it
  • Keep detaching and reattaching in hope
  • Write an older backup over the damaged one

Bench questions, straight answers.

My SQL database has gone into Suspect — where do I start?

First and foremost; take the database offline, then safely copy the MDF and LDF files before doing anything else. "Suspect" is simply a way of saying the database engine could not replay its transaction log tidily due to an unclean shut down. A suspect database can usually be recovered with ease. The best route to making sure a suspect database cannot be restored is to run a well intentioned but incorrect database repair on the original.

Is recovery possible with the transaction log missing?

Usually, yes. Almost every piece of data in a SQL Server database resides in the data file. While it may take some time and/or some effort, nearly every database can be put into a state which allows it to be attached by SQL Server without the log. However, transactions still open at the point of failure may be partial, and we will show you exactly where that line fell in your case.

Exchange reports Dirty Shutdown — is the mail lost?

Most likely not. A Dirty Shutdown indicates there are un-replayed log records for the database; a harmless header check names them, and a soft recovery replays whichever ones survive. Your email is usually all intact. The hard repair is a shortcut that may put your email at risk due to the potential for losing data.

Why does the corruption return once it's been repaired?

The reason for this is the database itself wasn't the problem; instead, the true cause is the storage underneath: when corruption keeps coming back it is nearly always a faulty disk, a degraded RAID set or a cache writing new damage to every 'repaired' version. Therefore, this is really a server recovery with the symptoms of a corrupted database, and we treat both.

Whatever has gone wrong, keep it switched off.

Powering a damaged device up again costs you data. Start by opening a case instead; diagnosis is always free, regardless of your decision.

0800 6890668