AS SQL Recovery & Repair Studio — SQL Database (MDF) Recovery Software

Yes. For MDF file repair it reads the damaged file page by page, shows which tables and rows are intact and writes the recovered data to a new database on your SQL Server. It can also rebuild a destroyed boot page and file header so that SQL Server attaches the file again.

If the database files were deleted from the disk, stop writing to that drive. Our free tool AS SQL Deleted Database Recovery scans the drive for the deleted database and packs it for our laboratory. If rows or a table were deleted inside a database that still exists, this program recovers them from the data file.

Copy the MDF, NDF and LDF files first, before any repair command. Then open the copy in the free edition: the database does not have to come online, and you see what can be recovered. A SQL database suspect state or SQL Server recovery pending usually means damaged pages, or a damaged or missing log file.

Yes. For BAK file recovery the backup file is opened directly, plain or compressed, also when part of it is damaged or encrypted. You can recover tables from it or convert the backup to an MDF.

Usually most of it. When a SQL database is corrupted the damage is normally limited to some pages, and the rows on all other pages are read directly from the file. Run the free analysis before any repair that allows data loss.

Copy the MDF (and any NDF files) to another disk and open the copy in the free edition. It classifies every page, shows the damage map and previews the tables and rows that can be recovered. With a licence the recovered data is written to a new SQL Server database, SQL scripts or CSV. The original file is only ever read.

Yes. The program reads the MDF / NDF files directly, so the database does not have to attach or come online. Take a copy of the files first, then analyse the copy to see which tables and rows are intact.

Not before you have a copy of the files. That option repairs the database by deleting damaged pages, and the rows on them are gone afterwards. Reading the file page by page first shows what is recoverable without changing anything.

Often. Deleted records are recovered from free space inside the data file, as long as SQL Server has not reused that space. The sooner the file is copied after the deletion, the more is found.

Often. On the SQL Server Tools page choose the database: the program reads it from a Windows snapshot, so the database stays online and nothing is written to it. A dropped table is found with its name and columns, and deleted rows are recovered from free space, as long as SQL Server has not reused that space. Do it as soon as possible after the mistake.

Yes. Choose "Add only the missing rows" when exporting: rows that are already in the table (same primary key) are skipped, nothing is replaced or deleted, and foreign keys are switched off for the insert and checked again afterwards.

Yes. On the SQL Server Tools page the data file is attached without its log file and SQL Server builds a new one. If SQL Server refuses, the file is opened directly and its tables are recovered instead.

No — the data files are read directly. SQL Server (any edition, Express included) is only used to write the recovered data into a new database and validate it.

Very often, partly or largely: many ransomware families encrypt only parts of large files. The program finds which pages are encrypted and recovers every row on the pages that survived. Rows on encrypted pages cannot be recovered without the key; they are listed as missing, never invented.

Yes. The program recognises SQL Server data and backup files by their content, not by their name, so files with an added ransomware extension open like any other. Do not rename or move the originals; work on copies.

Often. The backup is searched directly for every page image that is still intact, verified by its checksum, so a destroyed backup header does not stop it, and compressed backups are decoded too. On real LockBit-encrypted SQL Server 2019 backups it recovered 4,703,039 of 4,759,135 rows (98.8%), checked against a healthy copy of the same database.

It does not depend on the family: it measures which pages of each file are still intact and recovers the rows on them. We have used it on real files encrypted by LockBit, The Gentlemen, M142HIMARS and others. Rows on pages that were encrypted cannot be recovered without the attacker's key, and the program says so instead of guessing.

When the system catalog (the list of tables and their columns) was destroyed, an older copy of the same database — or one with the same schema — supplies that structure. Its data is never used as the customer's data.

No. Original files are only ever read; recovered data is written to a new database, scripts or CSV.

SQL Server 2008 to 2022 data files. The version is read from the file itself and shown in the analysis.

Your licence key (ASSQ-…) arrives by e-mail and in your account. Open Licence in the program, paste the key and click Activate.