Why DataNumen SQL Recovery?


#1 Recovery Rate

#1 Recovery
Rate

10+ Million Users

10+ Million
Users

20+ Years of Experience

20+ Years of
Experience

100% Satisfaction Guarantee

100% Satisfaction
Guarantee

Recover Much More than Our Competitors


Recovery rate is the most important criterion of an MS SQL Server recovery product. Based on our comprehensive tests, DataNumen SQL Recovery has the best recovery rate, much more better than any other competitors in the market!

Average Recovery Rate

Comparison Chart

Learn more about how DataNumen SQL Recovery smokes the competition

Our Customers' Testimonials

Extremely Simple Interface


Solution for Following Common Errors and Problems in SQL Server Database File


solutions

MORE


Free download100% Secure
Buy Now100% Satisfaction Guarantee

Main Features in DataNumen SQL Recovery v6.2


  • Support for Windows 95/98/ME/NT/2000/XP/Vista/7/8/8.1/10/11 and Windows Server 2003/2008/2012/2016/2019 operating systems.
  • Support Microsoft SQL Server 2005, 2008, 2008 R2, 2012, 2014, 2016, 2017, 2019.
  • Support to recover the schema/structure and data in the tables.
  • Support to recover all data types, including ASCII and Unicode XML data type.
  • Support to recover sparse column.
  • Support to recover deleted records in the database tables.
  • Support to recover indexes and primary keys.
  • Support to recover SQL database objects, including views, triggers, rules and defaults.
  • Support to recover stored procedures, scalar functions, inline table-valued functions, and multistatement table-valued functions.
  • Support to recover and decrypt encrypted objects in SQL Server databases.
  • Support to recover multiple files, including the MDF file (primary data file) and the NDF files (secondary data files).
  • Support to recover MS SQL Server database without a transaction log file (LDF).
  • Support to recover MDF/NDF data from undamaged or damaged VMWare VMDK(Virtual Machine Disk) files(*.vmdk), Virtual PC VHD(Virtual Hard Disk) files(*.vhd), Acronis True Image files(*.tib), Norton Ghost files(*.gho, *.v2i), Windows NTBackup files(*.bkf), ISO image files(*.iso) and Nero image files(*.nrg), with advanced algorithms.
  • Support to recover SQL Server data from temporary tempdb.mdf file.
  • Support English, Spanish, French, German, Italian, Portuguese, Russian, Japanese, Korean, Simplified Chinese and Turkish.
  • Support to recover MDF and NDF files as large as 16TB.
  • Support to repair SQL database files on corrupted media, such as floppy disks, Zip disks, CDROMs, etc.
  • Allow DBA to repair a batch of corrupt MDF files.
  • Integrated with Windows shell, so you can repair a corrupt SQL database with the context (right click) menu of Windows Explorer easily.
  • Support drag & drop operation when performing SQL data recovery.
  • Allow database administrators to recover SQL Server databases via command line (DOS prompt) parameters.

Free download100% Secure
Buy Now100% Satisfaction Guarantee

Using DataNumen SQL Recovery to Recover Corrupt SQL Server Databases


See Video Tutorial (Full Version)
See Video Tutorial (Demo Version)

When your MS SQL Server MDF files are corrupt or damaged and you cannot open them normally, you can use our SQL database recovery software to scan the MDF data files and recover as much data from them as possible.

Start DataNumen SQL Recovery.

DataNumen SQL Recovery

Note: Before recovering any corrupt MDF files with DataNumen SQL Recovery, please close any other applications that may modify the MDF files.

Select the corrupt or damaged MDF file to be repaired.

Select Source File

You can input the MDF file name directly or click the Browse button to browse and select the file. You may also click the Find button to find the MDF file to be repaired on the local computer.

If there are one or multiple NDF files associated with the damaged MDF file, then you can add them as well:

Select Source NDF File

If you know the format of the source SQL Server database file, then you can specify it:
Select Source Format

If you do not specify the format, then by default, DataNumen SQL Recovery will try to analyse the source SQL Server database file and auto-detect the format automatically.

By default, DataNumen SQL Recovery will save the fixed MDF file into a new file named xxxx_fixed.mdf, where xxxx is the name of the source MDF file. For example, for source MDF file Damaged.mdf, the default name for the fixed file will be Damaged_fixed.mdf. If you want to use another name, then please select or set it accordingly:

Select Destination File

You can input the fixed file name directly or click the Browse button to browse and select the desired location for the fixed file. Make sure there is enough disk space for it. You can estimate the required space based on the size of the corrupt SQL database.

After the data recovery process, you can start SQL Server Management Studio and access the corresponding recovered database.

Click the Start Recovery button, DataNumen SQL Recovery will prompt a "Connect to SQL Server" dialog box, as below:

Connect to SQL Server Dialog Box

You need to set the Server Name and Authentication for the SQL Server instance on the local or remote computer, then click the "OK" button. Our MDF recovery software will auto-detect the collation of the source database, then set the destination database collation accordingly. If it cannot auto-detect the collation, it will ask you to set it. Then it will scan the entire database, repair MDF file, and recover data with advanced algorithms. Progress bar

Progress Bar

will indicate the data recovery progress.

After the recovery process, if the source MDF file can be recovered successfully, you will see a message box like this:

Success Message Box

Now you start Microsoft SQL Server Management Studio and access the data in the recovered SQL Server database.

More Information


DataNumen SQL Recovery 6.2 is released on March 4th, 2022

  • Support Windows 11.
  • Fix some minor bugs.

DataNumen SQL Recovery 6.1 is released on November 28, 2021

  • Support Turkish.
  • Fix some minor bugs.

DataNumen SQL Recovery 6.0 is released on June 22, 2021

  • Support to remember the connection settings.
  • Support to recover primary keys.
  • Support to recover the nullable property of a column.
  • Fix some minor bugs.

MORE

Where can I find the recovered data?

The recovered data are output to a new database in the SQL Server instance you connect to when starting the SQL MDF recovery process.

The MDF file name of the output database is specified before you start the recovery.

Normally, you do not need to access the SQL database MDF file directly. After the recovery process, to access the recovered data, please do as follows:

  1. Start SQL Server Management Studio.
  2. Connect to the SQL Server instance which is same as the one you used to recover your corrupt database.
  3. After connection, click the instance.
  4. Then click Databases node.
  5. Then you will find one or some databases called “Database_Recovered_On_yyyy_mm_dd_hh_mm_ss_#”, where yyyy, mm, dd, hh, mm, ss is the time when the database is created, i.e., year, month, day, hour, minute and second. And # is a sequence number starting from 1. This information can easily help you identify the database generated from the latest recovery process.
  6. Click the node of the database you identify. You can then access all the recovered SQL database objects. For example, under Tables node, you can see all recovered database tables, including the schemas and the records.

How to reduce data loss during a SQL Server data disaster?

It is recommended to prepare a disaster recovery (DR) plan for your SQL Server instance, which normally includes:

  1. Routinely backup your SQL Server data.
  2. Have a professional SQL recovery tool such as DataNumen SQL Recovery on hand. Thus when you encounter SQL database corruption, you can use it to repair corrupt files and recover your data as soon as possible.
  3. Utilize the high availability features in SQL Server.

What are your product’s advantages over other MS SQL database recovery tools?

You can find a complete competitive comparison of our product with other MS SQL database recovery tools in the market.

Can I pause/resume the SQL database repair process?

That is not possible. If a repair process has been started, then you can either abort it or let it complete. Later if you want to re-repair the same SQL database file, then you need to re-start the repair process from the beginning.

However, during the repair process, you can see the recovered data in SQL Server management studio at the same time. If you think all the wanted data are recovered, then you can abort the repair process to save your time, without damaging the output database.

I only have the SQL MDF file, the transaction log (LDF) file is lost. What to do?

DataNumen SQL Recovery can recover your data from corrupt MDF file without the transaction log (LDF) file. So if your transaction log file is lost, that will not be a problem.

Do you support to recover data record in XML type?

Yes, our SQL database recovery software supports to recover records in both ASCII and Unicode XML data types.

Do I need to be an database administrator (DBA) to perform the recovery?

Yes, you need to be the database administrator (DBA), or at least get the following information from the database administrator (DBA):

  1. SQL Server instance name(Server Name)
  2. Authentication of the SQL Server instance.

Thus you can use this information to connect to the SQL Server instance and perform the recovery.

Does Microsoft SQL Server has a built-in tool to recover a corrupt database?

Yes, they do have the built-in dbcc commands, i.e., dbcc checkdb and dbcc checktable, which can check table schemas and records, then fix minor issues in your corrupt database or database tables. However, these tools only work for a very limited number of cases. If they cannot repair MDF file corruption, then you’d better to try DataNumen SQL Recovery, which works much more better.

Some of the basic usages of dbcc checkdb are listed below:

Command Usage
dbcc checkdb(‘MyDB.mdf’) Check if MyDB.mdf has any issues.
dbcc checkdb(‘MyDB.mdf’, REPAIR_ALLOW_DATA_LOSS) Check MyDB.mdf. If there are any issues, repair MDF database file, which may cause data losses.
dbcc checkdb(‘MyDB.mdf’, REPAIR_REBUILD) Check MyDB.mdf. If there are any issues, repair MDF database file, which will NOT cause data losses, but may take more time.

Some of the basic usages of dbcc checktable are listed below:

Command Usage
dbcc checktable(‘MyDB.MyTable’) Check if MyTable in MyDB has any issues.
dbcc checktable(‘MyDB.MyTable’, REPAIR_ALLOW_DATA_LOSS) Check MyTable in MyDB. If there are any issues, repair the table, which may cause data losses.
dbcc checktable(‘MyDB.MyTable’, REPAIR_REBUILD) Check MyTable in MyDB. If there are any issues, repair the table, which will NOT cause data losses, but may take more time.

How much disk space do I need prepare for the output database?

First, you need to calculate the total size of the source data, including the SQL database MDF file and all the associated NDF files. Assuming that is SDataSize.

Then, based on the SDataSize, you should prepare at least 2 * (SDataSize * 110%) for the output database on your desired location, including both the SQL MDF file and the LDF file.

Why my SQL Server database gets corrupt?

There are many reasons that may cause SQL database corruption, including:

  1. Hardware reasons: such as power failure, bad sectors on disks, hard disk failures, unexpected system shutdown, etc.
  2. Software reasons: such as software defects, virus infections, ransomware attacks, backup failure, invalid database file header, etc.

DataNumen SQL Recovery is able to recover data for all the above cases.

What is the format of the recovered files?

DataNumen SQL Recovery will connect to SQL Server instance and utilize it to generate the recovered database. So the format of the recovered files is same as the SQL Server version of the instance you connect to when performing the recovery. For example, if you connect to SQL Server 2000 instance, then the output database will also be in SQL Server 2000 format.

Which versions of SQL server are supported?

DataNumen SQL Recovery support to recover SQL databases created by the following versions of MS SQL Server: SQL Server 2005, 2008, 2008 R2, 2012, 2014, 2016, 2017, 2019.

It can connect to the following versions of SQL Server instances to generate the fixed database: SQL Server 2000, 2005, 2008, 2008 R2, 2012, 2014, 2016, 2017, 2019. The fixed database will be saved in the version same as that of the SQL Server instance.

Can you output the recovered database as a SQL script?

The earlier versions of DataNumen SQL Recovery support such a feature. However, we have removed this feature in the recent versions.

Do you support to recover indexes and other objects?

Yes, indexes, primary keys, views, triggers, rules, defaults, stored procedures, and other objects are supported.

I fail to recover SQL database with your file recovery tool. Please help.

Please contact us and provide the recovery log. You can find more details on how to get the recovery log.

Sometimes, due to the data disaster, the MDF file and NDF files may not contain the actual SQL data. But the disk or drive where you have stored the MDF or NDF files may still contain recoverable data. You can recover your data from the disk or drive directly.

Can I save the recovered database into multiple data files?

Sorry but currently our corrupt SQL database recovery tool does not support to save the recovered database into multiple data files, i.e., one primary data file (MDF) and several secondary data files (NDF).

However, after the SQL MDF recovery process is completed, you can do as follows to implement your goal:

  1. Start SQL Server management studio.
  2. Create a new database and design the files and filegroups based on your requirements, such as spread data across several files.
  3. Clone the recovered database from the recovered database to the new database created in step 2. Alternatively, you can also export the recovered database as a SQL script, and then import the script back to the new database.

What are the limitations of the demo version?

The demo version uses the same data recovery engine as the full version, except that it will insert demo texts in some of the fields in the recovered database.

Can you recover the table schema only?

Our SQL database recovery software will recover the entire database, including tables and all other objects. For tables, both the table schema and the table record data will be recovered. It is not possible to recover the table schema only.

Which versions of Windows are supported?

Currently, Windows 95/98/ME/NT/2000/XP/Vista/7/8/8.1/10/11 and Windows Server 2003/2008/2012/2016/2019 operating systems are supported. Also, both 32bit and 64bit systems are supported.

Can you output the database as one MDF and multiple NDF files?

Sorry but currently we only support to output a single SQL MDF file.

Your file recovery tool shows an error when recovering an index. How to solve the problem?

Some indexes have some special constraints, such as unique, while the recovered data may not meet these constraints. After the SQL MDF recovery process, you can do as follows to solve the issue:

  1. Remove some redundant data to make sure the remaining data meet the constraints. Then rebuilt the index manually.

or

2. Remove some constraints in the index and rebuild it manually.

You can do both 1 and 2 with SQL scripts.

I only have the corrupted MDF file. The associated NDF files are missing. Can you recover the data?

Yes, even if you only have the primary database file, our MDF recovery software can still recover data for you. However, only those in the MDF file can be recovered. Those in the NDF files are beyond recovery since you do not have the NDF files.

Can you recover encrypted objects?

Yes, we can. And the encrypted objects, such as stored procedures, will be recovered and saved as decrypted versions.

Can you recover deleted records?

Yes, by default, our file recovery tool will recover deleted records. You can also change the option, as follows:

  1. Start our SQL MDF recovery tool.
  2. Click “Options” tab.
  3. Check/Uncheck the “Recover deleted records” option accordingly.
  4. Repair MDF files.

What if I don’t know the version of the SQL Server database?

No worries. Our MDF recovery software will auto-detect the version for you, before it starts to repair corrupt databases.

Can you output the recovered data as .CSV files?

Sorry but currently our SQL database MDF recovery software does not support to do so. But you can export your table to .CSV files in SQL Server Management Studio directly.

How long can I use the full version?

The license for the full version is perpetual. You can use it forever and for unlimited times.

What are the consequences of SQL database corruption?

There are many:

  1. Data losses.
  2. Performance degrades.
  3. Some operations may fail. Such as backup, replicate, etc.

How to detect MDF file corruption?

If you encounter any of the problems in the list, then your MDF file is corrupt. Moreover, you can also use the following command to detect the MDF file corruption:

SELECT * FROM msdb..suspect_pages WHERE (event_type = 1);

Different event types correspond to different errors, as below:

Event type Error
1 823 or 824 error
2 Bad checksum
3 Torn page

Note the above command can only detect minor corruptions in MDF files.

Can you recover MDF files attacked by Ransomware?

Ransomware is a kind of malware. It will encrypt your MDF database files. You need to pay the creator of the Ransomware to decrypt your database and get back your data.

Fortunately, our SQL database recovery software can recover data from MDF files infected by Ransomware.

More Articles in Knowledgebase