Welcome

EaseUS MS SQL Recovery is an easy-to-use application designed to repair corrupt or damaged Microsoft SQL Server database (MDF) files in a safe and non-destructive manner. It uses powerful algorithms to perform a thorough scan of MDF files so as to recover as much data as possible. The software never deletes or modifies original data and even heavily damaged files can be optimally repaired and restored. 

Getting Started

Before using EaseUS MS SQL Recovery, let us have a basic idea of what the software does, system requirements and steps to run the software, activate the software, etc. This way you will be able to use the software more efficiently.

Hardware Requirements

Hard Disk: At least 100 MB of free disk space

RAM: 2 GB minimum (4 GB recommended)

System Requirements

Make sure you are running any one of the listed operating systems.

Windows XP®

Windows Vista®

Windows® 7

Windows® 8

Windows® 8.1

Windows® 10

Windows® Server 2000

Windows® Server 2003

Windows® Server 2008

Windows® Server 2012

Windows® Server 2016

Supported MS SQL Versions

The versions of MS SQL Server below are supported by the software:

MS SQL Server 2019

MS SQL Server 2017

MS SQL Server 2016

MS SQL Server 2014

MS SQL Server 2012

MS SQL Server 2008 R2, 2008, 2008 (64 bit), 2008 Express

MS SQL Server 2005, 2005 (64 bit), 2005 Express

Activation

Install and run the trial version, click shopping cart icon, input the license code and complete the activation.

Repair Damaged MS SQL Database

1. After running the software, you will get this prompt if your computer has MS SQL Server installed.

2. Click "Start" -> "Microsoft SQL Server" -> "SQL Server Configuration Manager", choose SQL Server Services and right click on SQL Server to stop it.

Or input command line in CMD to stop the service:

net stop MSSQLSERVER

3. Click ".." button and Browse the .mdf file, or click Search to find it on your computer.

4. Select the right database and click Analyze.

5. You are able to view the content of the database after recovery.

6. Click "Export" and save it as a new database or export to the existing database. You can also export it to SQL script file.

7. Restart SQL Server service and verify the recovered database.