MS SQL database recovery software

Answer:

Repairing a database in MS SQL Server format from several source files

A database in MS SQL Server format contains one or several files. There are several types of files: main data file (with *.mdf default extension), secondary data file (with *.ndf default extension) and a transaction log file (with *.ldf default extension). If you'd like to repair data with Recovery Toolbox for SQL Server, you should specify the path to all secondary data files and the main data file. It can be made with Open File dialog box.

If corrupted database contains the main data file, a secondary data file(s) and a transaction log file(s), you should select the main data file of *.mdf format and all secondary data files of *.ndf format (see fig. 2).

Answer:

A lot of RAM is required to recover large MS SQL Server databases. The developers of the program recommend that you recover large databases on computers with enough free physical memory. The physical memory used by the program must not be less than the size of the file you are recovering divided by 500 plus 20-100 MB more for the program to run. That is, if you try to recover an .mdf file with the size of 100 GB, the computer must have at least (100 GB / 500) + 120 MB = 320 MB of free physical memory.

Answer:

To fix this problem, you should:

1. Save the data as scripts
2. Run the file install.bat with all the necessary parameters from the command line
3. See response files ( *????.sql.txt) to find out which scripts have not been executed successfully
4. Load scripts executed with errors into Query analyzer from Microsoft SQL Server and try to execute them there. After you get an error message, you should detect which command causes the error. If this command writes data that is of no value, you can simply remove it from the file. Otherwise you should send the script executed with errors and a screenshot from Query analyzer to the developers. Besides, it may later be necessary to send the source *.mdf file to the developers for them to study the problem.

Answer:

• If a value in a Primary Key field is incorrect (for example, it is negative or several dozen times greater than all other values), it means that the source data were seriously damaged and it is impossible to recover it completely.
• If duplicate values appear in Primary Key fields, it means that the program has recovered sheets with data that should have been marked for deletion in the database (mdf, ndf files). But actually there is no mark that the sheet with data should be deleted. And therefore the program recovers data from all sheets. It results in excessive recovered data and the developers of Recovery Toolbox for SQL Server could not find criteria for filtering out excessive entries. In this case, database administrators and/or software developers make the final decision about excessive entries in the recovered database that should be deleted.

Answer:

The tool isqlw.exe is a component of the MS SQL Server package. You can always download the latest version of MS SQL Server from the Microsoft site and install the necessary components on the computer. The demo version of MS SQL Server downloaded from the Microsoft site allows you to use the components within the period specified in the EULA.

If you can find the appropriate tools on Microsoft.com then you can download and install Query Analyzer from our website. The link for download is: https://recoverytoolbox.com/download/isqlwInstall.exe

Answer:

It is possible that something additionally happens with your MDF between tryout and registration (recovered by other software or something else). You can check it by running the demo version against this file on another computer.

If you see the following error after running your scripts:

Server: Msg 242, Level 16, State 3, Line 1

[Microsoft][ODBC SQL Server Driver][SQL Server] The conversion of a char data type to a datetime data type resulted in an out-of-range datetime value.

The statement has been terminated.

Answer:

It means that you should change the server language settings by doing the following:

1. Start Enterprise Manager.
2. Select the necessary server and connect to it.
3. Open its properties window by clicking the right mouse button on it and selecting Properties.
4. Open the Server Settings tab.
5. Select English in the Default Language for user dropdown list and press OK.

6. Stop SQL server. To do that, select Stop in the context menu and answer Yes to the question Are you sure you wish to stop SQL Server service. in the confirmation window.
7. Start SQL Server. To do that, select Start in the context menu.
8. Now you can run scripts saved on your hard drive by Recovery Toolbox for SQL Server. You can also run the program in the database scripts execution mode.

9. Now you need to restore the settings. To do that, open the properties window of the necessary server in Enterprise Manager.
10. Select the default language in the Default Language for user list and press OK.

11. Stop SQL server. To do that, select Stop in the context menu and answer Yes to the question Are you sure you wish to stop SQL Server service. in the confirmation window.
12. Start SQL Server. To do that, select Start in the context menu.

If you see the following error after running your scripts:

Server: Msg 242, Level 16, State 3, Line 1

[Microsoft][ODBC SQL Server Driver][SQL Server] The conversion of a char data type to a datetime data type resulted in an out-of-range datetime value.

The statement has been terminated.

Answer:

It means that you should change the server language settings by doing the following:

1. Start Management Studio.
2. Choose the necessary server.
3. Go to Security\Logins.
4. Choose the user that will be using the database and open the user's properties window.
5. Select English in the Default Language for user dropdown list and press OK.

6. Now you can run the script saved on your hard drive by Recovery Toolbox for SQL Server. Alternatively, you can start the program in the database scripts execution mode.

7. Now you need to restore the settings. To do that, open the properties window of the necessary user Management Studio.
8. Select the default language in the Default Language for user list and press OK.

Answer:

Simply copying or restoring data tables from an MSDB database on a new server does not allow to restore DTS Packages because they have interior connections to the execution context of the server on which they were created and on which they were used on it prior to migration. To copy DTS Packages between servers, VB scripts must be employed. Therefore, the program Recovery Toolbox for SQL Server is not suitable for restoring DTS Packages.

Answer:

Recovery Toolbox for SQL Server automatically detects the server version the database was used on. Therefore, if the database was used on MS SQL Server 2000, the program writes the isqlw tool to the saved scripts for importing into the new database. If the database was used on MS SQL Server 2005 or higher, the sqlcmd tool is used in the scripts. If you want to import data to a database on a server with a version different from the original one, you should use the tool for the corresponding server:

• Isqlw - for MS SQL Server 2000
• Sqlcmd - for MS SQL Server 2005 and higher

Answer:

1. Start SQL Server Management Studio
2. In Object Explorer right click on Databases
3. Click on Attach
4. Click Add button
5. Select the mdf file and click Ok button
6. Click Ok button
7. Wait for operation complete.

Answer:

Recovery Toolbox for SQL Server can partially or fully recover information from .MDF/.NDF files of Microsoft SQL Server database files encrypted by ransomware viruses.

Recovery Toolbox for SQL Server does not decrypt data.

In general, data decryption is not applicable in these cases.

However, Recovery Toolbox for SQL Server can be useful in cases when the MDF file was partially encrypted. Typically, viruses only encrypt the header and/or beginning of files because of their large size. In these cases, if only the header or part of the MDF file was encrypted, Recovery Toolbox for SQL Server can be helpful. The program analyzes all the data blocks and collected data structure in the file. Then, it recreates the original data structure and the data itself, if possible.

Microsoft SQL Server MDF file structure

Is it Possible to Recover Data from an MDF File after an Attack by a Ransomware Virus?

There is no guarantee that you can recover 100% of the data or some part of it by using the program. To get a definite answer to that question, you need to download the DEMO version of Recovery Toolbox for SQL Server, specify the encrypted MDF file and wait for the analysis of the file to complete.

Upon completion of the analysis of the .mdf file in the DEMO version of the program, a full preview of the data that can be extracted from the file is available.