Univik SQL Database Recovery

Excellent TrustRating 4.8 (276 reviews)

Repair Corrupt MDF Files and Recover Lost SQL Server Data

Univik SQL Database Recovery repairs corrupt and suspect SQL Server MDF files at the binary level and brings back data that SQL Server has lost. Recover deleted records, rebuild dropped tables and read past torn pages with no SQL Server, no attach and no LDF log file. When the data is back, export or restore it in a click.

Free Download
100% Safe & Secure

Buy Now
Starting from $99

*Free trial lets you load a damaged file and preview the recovered tables. A license unlocks unlimited recovery, starting from $99.

No SQL Server Needed: No attach, no restore and no LDF log file. Read the MDF straight from disk.
Repair Corrupt and Suspect Files: Reverse torn page bits and read past damaged pages to pull out every readable row.
Recover Deleted and Dropped Data: Bring back deleted rows shown in red and rebuild dropped tables with their schema.
Read Only and Safe: The original file is never changed, so it stays safe for another attempt or for evidence.

Univik SQL Database Recovery box

VirusTotal Verified Safe

Certified clean by 70+ antivirus engines. No malware, spyware or adware.

Recovers Data From Every SQL Server Version

SQL Server 2022

SQL Server 2019

SQL Server 2017

SQL Server 2016

SQL Server 2014

SQL Server 2012

SQL Server 2008 R2

SQL Server 2008

SQL Server 2005

SQL Server 2000

Product Screenshots

See the Recovery In Action

A quick look at the app as it opens a damaged file, brings back deleted records and dropped tables, then hands the data over for export.

Recovered deleted records shown in red in the data grid

Deleted records recovered and shown in red, with a per table count

Recovered dropped table with its schema and rows

A dropped table rebuilt with its schema and surviving rows

A suspect MDF file opened with all tables loaded

A suspect file opened directly, with every table loaded

Recovered data ready to export or restore to SQL Server

SQL Recovery

Repair SQL Database and Recover Lost Data

One recovery tool for every MDF problem, from a database marked suspect to a table someone dropped by mistake.

Repair Corrupt MDF Files

Reverse torn page protection bits and read past damaged pages so a corrupt MDF file opens and gives up its rows.

Open a Suspect Database

When SQL Server marks the database suspect and will not attach, read the MDF directly and pull the data out.

Recover Deleted Records

Bring back rows deleted from any table, including rows found after ghost cleanup, shown in red with a count.

Recover Dropped Tables

Rebuild a dropped table with its name, full schema and surviving rows from catalog remnants left in the file.

Read an Orphaned MDF

Open an MDF that was detached, copied or left behind after a server failure, with no matching LDF needed.

Bulk Scan Many Files

Check many MDF files in one pass and see which ones are readable, with clear warnings about what is damaged.

Deleted Records

Recover Deleted Records in SQL Server

Rows deleted from a table are not gone right away. The recovery engine finds them and marks them clearly.

Deleted records recovered and shown in red with a per table count

Deleted rows, brought back in red

Finds ghost records that SQL Server marked for cleanup
Also finds deleted rows after ghost cleanup by walking the physical record layout on each page
Works on both fixed width and variable width tables
Each table shows its recovered count, for example 123 rows 6 deleted
A one click filter shows only tables that contain deleted records
Recovered rows export apart from live data so nothing mixes silently

Dropped Tables

Recover a Dropped Table in SQL Server

A dropped table leaves traces in the file. The engine reads those traces and rebuilds the table.

A dropped table rebuilt with its schema and rows

Dropped tables, rebuilt from remnants

Recovers dropped table names from catalog data pages and catalog name index pages
Rebuilds the full column schema from surviving catalog entries
Re-links surviving data pages when the file was saved before the space was reused, restoring the actual rows
Dropped tables appear in the list in red with a deleted label
Reports how many dropped tables were recovered when the file loads

Repair

Repair Corrupt and Suspect MDF Files

When a database is marked suspect and will not attach, the engine still reads past the damage and pulls out every readable row.

Torn Page Recovery

Reverses SQL Server torn page protection bits before any parsing so a damaged file reads correctly.

Damaged Slot Arrays

Recovers rows from pages with broken slot arrays by scanning the page body directly.

Row Header Healing

Heals corrupted row headers with evidence based checks, so healthy data is never altered.

Forwarded Records

Handles rows moved by updates so they are never lost or counted twice.

Large Value Reads

Reads large text, ntext and image values through record pointers with a fallback scan for older formats.

Validated Recovery

Recovery is checked against SQL Server internal row counters so the counts you see are accurate.

Error States

Recover Data From Common SQL Server Errors

When SQL Server throws one of these, the database will not come online, but the MDF file still holds your data. Open it here and export the tables.

SQL Server state or error	What it means	How recovery helps
Database marked suspect	The database failed to recover on startup and is offline.	Read the MDF directly and export the tables.
Stuck in recovery pending	SQL Server cannot start recovery, often a missing file or resource.	Pull the data from the MDF without bringing the database online.
Cannot attach without LDF	The log file is missing or corrupt so attach fails.	No LDF is needed. The MDF is read on its own.
Error 5171	The file is reported as not a primary database file.	Open it at the binary level and recover readable rows.
Error 823 and 824	An I/O or logical consistency error, often a torn page.	Reverse the torn page bits and read past the bad page.
Error 9004	An error while processing the transaction log.	The log is not used, so recovery still reads the MDF.

Recovery is read only. The original file is never changed, so you can still try other options afterward.

How It Works

How SQL Database Recovery Works

Four steps from a broken file to your data back in hand.

Step 1: Load the Damaged MDF File

Select the corrupt, suspect or detached MDF file. No SQL Server and no LDF log file is needed.

Step 2: Scan and Recover

The engine reverses torn pages, walks the record layout and scans catalog remnants for lost data.

Step 3: Review Recovered Data

Browse the tables. Deleted rows show in red and dropped tables appear with a deleted label.

Step 4: Export or Restore

Export the recovered tables or restore them straight back into a live SQL Server database.

Quick Start Guide

Download and install: Install on Windows 10 or 11 with .NET Framework 4.8 or higher. No SQL Server required.
Open the damaged file: Select the corrupt or suspect MDF. Recovered deleted rows and dropped tables show in red.
Check what was found: Each table shows a recovered count and a clear warning about any damage.
Get the data back: Export the recovered tables or restore them to SQL Server.

Comparison

Univik vs DBCC CHECKDB and Manual Repair

See how safe recovery compares to the built in repair commands.

Univik SQL Database Recovery

No Data Loss: Read only recovery that never deletes a page to force consistency.
No LDF Needed: Reads the MDF on its own when the log file is gone.
No Running Server: Works even when the database will not come online.
Reads Suspect Files: Opens a database that SQL Server refuses to attach.
Recovers Deleted and Dropped: Brings back rows and tables that queries cannot see.
Original Kept Safe: The file is never changed, so evidence stays intact.

DBCC CHECKDB and Manual Repair

Risky Repair: REPAIR_ALLOW_DATA_LOSS can delete pages to make the database consistent.
Needs the Database Online: The database has to attach first, which suspect files will not do.
Needs the Log: Many recovery paths need a healthy LDF file.
No Deleted Recovery: It cannot bring back rows that were already deleted.
No Dropped Table Recovery: A dropped table is gone from the live catalog.
Changes the Original: Repair writes into the live database file.

Use Cases

Who Uses SQL Database Recovery

Real situations where getting the data out of a broken MDF saves the day.

DBA in an Outage

The database is suspect and will not attach. Pull the tables out and get the business running while you rebuild.

Records Deleted by Mistake

Rows were deleted and there is no fresh backup. Recover them from the file before the space is reused.

A Table Was Dropped

Someone dropped a table and the backup is old. Rebuild its schema and rows from what is left in the file.

Forensic and Evidence Work

Examiners must read a damaged database without altering it. Read only recovery keeps the original intact.

MSP or Support Desk

You handle many client servers. Bulk scan a batch of MDF files and see which ones can still be read.

Developer With a Suspect DB

A dev or staging database went suspect. Recover the tables and restore a clean copy without a full rebuild.

Technical Data Sheet

Recovery Tool Specifications

Product details, system requirements and compatibility.

Product Name:	Univik SQL Database Recovery
Version:	6.7 (Latest)
File Size:	18.4 MB
License Delivery:	Instant via Email
License Price:	Starting from $99 Buy Now
Free Trial:	Free Download 100% Safe & Secure

Recovery Engine

What It Recovers

Corrupt and suspect files
Deleted records in red
Dropped tables
Torn and damaged pages
SQL Server 2000 to 2022

Input File:	MDF (corrupt, suspect, detached, orphaned or offline SQL Server primary data file), collation detected automatically
Recovered Output:	Recovered tables written to new files or restored to SQL Server. No LDF log file required.

Platforms:

Windows: 11 and 10 (64-bit)
Server: 2016 and later

Prerequisites:

.NET Framework: 4.8 or higher
No SQL Server: No SQL Server or SSMS needed
Access: Read access to the MDF file, nothing else

Pricing

Recovery Licenses Start at $99

Try recovery free, then unlock the full recovery and export when you are ready.

Free Trial

Load a damaged MDF file
Run recovery and preview tables
See recovered deleted rows
Evaluate before you buy

Free Download

What Our Customers Say

Feedback from DBAs, forensic examiners and support teams.

Martin H.

Database Administrator, Manchester, UK

"A production database went suspect on a Monday morning and would not attach. This read the MDF straight away and let me export every table. We were back up before lunch."

Neha R.

Digital Forensics Analyst, Pune, India

"I recover data from damaged databases for case work. The read only mode keeps the original file untouched. The recovered deleted records are exactly what I need to report."

Tomasz K.

MSP Engineer, Warsaw, Poland

"We support dozens of small business servers. The bulk scan tells me which MDF files are readable in minutes, so I know where recovery is possible before I promise anything."

Data recovered? Export or restore it.

Once your tables are back, save them as CSV, Excel, SQL script, JSON, XML, Parquet or Access, then restore them to a live server with Univik MDF Converter, which shares the same engine. Just need to look inside a healthy file? Use the free MDF Viewer.

Open MDF Converter

Help & Support

SQL Recovery Questions

Common questions about SQL Database Recovery.

Yes. SQL Database Recovery reads the MDF file directly at the binary level, reverses torn page protection bits and scans past damaged pages. It opens files that SQL Server marks suspect or will not attach and extracts every readable row to new files.

Yes. It finds ghost records that SQL Server marked for cleanup and also finds deleted rows after ghost cleanup by walking the physical record layout on each page. Deleted records show in red with a per table count and export apart from live data.

Yes. It scans catalog remnants to recover dropped table names, rebuilds the full column schema from surviving catalog entries and re-links surviving data pages when the space was not reused. Dropped tables appear in red with a deleted label.

Yes. When a database is stuck in recovery pending or suspect mode it will not come online, but the MDF file on disk still holds the data. SQL Database Recovery reads that file directly and exports the tables, so you get your data without bringing the database online.

Yes. No LDF log file is needed. The tool reads the MDF file on its own, which is useful when the log file is missing, deleted or corrupt and SQL Server cannot attach the database.

REPAIR_ALLOW_DATA_LOSS can delete pages to make a database consistent, which loses data. SQL Database Recovery is read only. It never changes the original file and writes recovered data to new files, so nothing is deleted and the original stays intact for another attempt or for evidence.

Recovery works with MDF files from SQL Server 2000, 2005, 2008, 2008 R2, 2012, 2014, 2016, 2017, 2019 and 2022. Damaged files from any of these versions are read at the binary level and the collation is detected from the boot page so text decodes correctly.

No. The MDF file opens in read only mode and is never modified. All recovered data goes to new files you choose. This makes the tool safe for forensic and evidence work.

Recovered tables can be exported to CSV, Excel, SQL script, JSON, XML, Parquet or Access. They can also be restored straight into a live SQL Server database. The export and format work is handled by Univik MDF Converter, which shares the same engine.

No. There is no SQL Server, no ATTACH and no RESTORE needed. You only need read access to the MDF file and .NET Framework 4.8 or higher on Windows. New to the format? See our MDF file guide.

Still have questions? Contact support or Live Chat