Recovery for SQL Server

Frequently Asked Questions

Table Of Contents
Questions And Answers

Can Recovery for SQL Server repair my SQL Server database, backup and log?

What limitations does the demo version of Recovery for SQL Server have?

I have tried the demo. How do I decide whether to purchase the full version of Recovery for SQL Server?

What are the differences between product licenses?

Why do results of recovery contain less data than the original SQL Server database, backup and log?

Running Recovery for SQL Server from command line (through Windows Start -> Run menu).

After running Recovery for SQL Server on the corrupted database, backup and log, a folder with sql script(s) and batch file has been created. How could these files be transfigured into a new database, backup and log?

When trying to execute the commit.bat file created by Recovery for SQL Server I receive the error which claims that isql.exe utility cannot be found. What should I use instead of missing program?

I have 3 databases, backups and logs in hand: MDF, NDF, LDF. Which one should I use to recover my database information?

The corrupted database, backup and log consists of a large number of records. Is there a way to set the number of sql scripts that Recovery for SQL Server creates during recovery session?

Recovery for SQL Server Error Messages

Recovery for SQL Server Error: Internal Program Error message.

Recovery for SQL Server Error: Not enough disk space.

SQL Server Error Messages

Error 5172

Error 5173

Error 823

Error 5172

Error 5181

Error 3243

The media family on device '' is incorrectly formed. SQL Server cannot process this media family. RESTORE DATABASE is terminating abnormally.

Questions And Answers

 
Q: Can Recovery for SQL Server repair my SQL Server database, backup and log?
A:

The effective way to find out if a SQL Server database, backup and log is recoverable is to try the demo version of Recovery for SQL Server on it. Visit the Demo page for a free copy of the demo.

Product specifications with lists of items recovered and not recovered is available at the Product Information page.

Note: Always backup your original corrupted SQL Server database, backup and log before proceeding with any recovery activity!

 
Q: What limitations does the demo version of Recovery for SQL Server have?
A: The demo version recovers a limited number of rows in each table. The remaining rows will contain "demo" in text fields and null values in other types of fields. Full version of Recovery for SQL Server will recover the demo-limited rows as well.

No additional tables or records are recovered by commercial version of Recovery for SQL Server if not present in demo output.

 
Q: I have tried the demo. How do I decide whether to purchase the full version of Recovery for SQL Server?
A:

Evaluating the results of demo recovery can help in making the decision.

 
Q: What are the differences between product licenses?
A:

Details of current licensing scheme are described at the Licensing page.

 
Q: Why do results of recovery contain less data than the original SQL Server database, backup and log?
A: This is normal. The damaged parts of your SQL Server database, backup and log will convert to zero size on output. The other common reason of file size decrease is when some of features of the original database, backup and log are not supported and therefore absent from the recovered database, backup and log.
Demo-recovered database, backup and log is smaller because it mostly consists of demo placeholders than actual data.
 
Q: Running Recovery for SQL Server from command line (through Windows Start -> Run menu).
A:

If your license type is Enterprise or Service, you can run Recovery for SQL Server from command line and use these calls in your batch files. Standard version does not support command line. The format for command line call is:

msr.exe <original filename with path> "<path to directory to store the recovered file(s)>"
(without angle brackets).

Please note that the directory for recovered file(s) should be created before starting the recovery.

Command line mode supports patterns '*' (replaces group of symbols) and '?' (replaces one symbol).

 
Q: After running Recovery for SQL Server on the corrupted database, backup and log, a folder with sql script(s) and batch file has been created. How could these files be transfigured into a new database, backup and log?
A:

To recreate database, backup and log, process resulting sql scripts starting with schema.sql and following by dataNNNN.sql. The database, backup and log will be recreated from scratch.

To make the import procedure more convenient for the end-user an appropriate batch file is automatically created and put in the same folder as sql script(s).

 
Q: When trying to execute the commit.bat file created by Recovery for SQL Server I receive the error which claims that isql.exe utility cannot be found. What should I use instead of missing program?
A: This could happen if you are using SQL Server 2005. The isql.exe and osql.exe utilities are replaced by sqlcmd.exe in this release.

To execute our batch file and recreate database automatically, please, do the following: create a link to the sqlcmd.exe called isql.exe and rerun commit.bat file. Alternatively, you can edit the batch file manually to make it use sqlcmd.exe instead of isql.exe.

About sqlcmd.exe on Microsoft.com:

 
Q: I have 3 databases, backups and logs in hand: MDF, NDF, LDF. Which one should I use to recover my database information?
A:
  1. MDF is for SQL Server Master Database File
  2. NDF is for SQL Server Secondary Data File
  3. LDF is for SQL Server Transaction Log File

Recovery for SQL Server requires MDF file to recover database, backup and log. If you don't have an MDF, there's no way to restore your data.
In case you have an NDF, please, place it in the same directory as MDF before processing with data recovery: Recovery for SQL Server will use it to improve the quality of recovery as much as possible.
LDF file is not necessary at all.

 
Q: The corrupted database, backup and log consists of a large number of records. Is there a way to set the number of sql scripts that Recovery for SQL Server creates during recovery session?
A: Recovery for SQL Server creates equal or less than 9999 sql scripts. By default, each script contains 2000 lines. To change the maximum size of the split script(s), set the MaxLines system registry value (type REG_DWORD) in the HKEY_CURRENT_USER\Software\Recoveronix\MSSQLRecovery key.

Recovery for SQL Server Error Messages

 
Q: Recovery for SQL Server Error: Internal Program Error message.
A:

Run Recovery for SQL Server in a logged mode and contact our support team with detailed description of the problem and the log file.

To create log file, please hold the SHIFT key while clicking the Recover button on the toolbar of Recovery for SQL Server or selecting the Recover: item in the main menu. You can also press CTRL+SHIFT+R after launching Recovery for SQL Server.

 
Q: Recovery for SQL Server Error: Not enough disk space.
A:

To fix this problem you need to set temporary directory to the drive with free space available (2-3 times of the original database, backup and log size). Fix the Windows environment variable to use it. Do the following:

  1. Open System in Control Panel.
  2. On the Advanced tab, click Environment Variables, then click the name of the user variable (TEMP or TMP) you want to change.
  3. Click Edit to change value.
  4. Set path to the location where temporary data should be stored (e.g., e:\).
  5. Restart computer for changes to take in effect.
  6. Run the software again.

You can also use the special environment variable called OFFICERECOVERY_TMP to set the directory where Recovery for SQL Server should store its temporary files. Use the method shown above to add/edit environment variable.

SQL Server Error Messages

 
Q: Error 5172
A: The header for the file '*.MDF' is not a valid database file header. The PageAudit property is incorrect. Could not restart database ''. Reverting back to old status.
ALTER DATABASE statement failed.
 
Q: Error 5173
A: Cannot associate files with different databases.
Could not restart database ''. Reverting back to old status.
Log file '*.LDF' does not match the primary file. It may be from a different database or the log may have been rebuilt previously.
 
Q: Error 823
A: I/O error (torn page) detected during read at offset 0000000000000000 in file '*.MDF'.
 
Q: Error 5172
A: The header for the file '*.MDF' is not a valid database file header. The BACKUP LSN property is incorrect. Could not restart database ''. Reverting back to old status.
ALTER DATABASE statement failed.
 
Q: Error 5181
A: Could not restart database ''. Reverting back to old status.
ALTER DATABASE statement failed.
Device activation error. The physical file name '*.LDF' may be incorrect.
 
Q: Error 3243
A: The file on device '' is not a valid Microsoft Tape Format backup set.
RESTORE FILELIST is terminating abnormally.
 
Q: The media family on device '' is incorrectly formed. SQL Server cannot process this media family. RESTORE DATABASE is terminating abnormally.
A: All versions of SQL Server

Product Guide

Recovery for SQL Server

Product Home

Product

Product information
Free demo version is available:
Download

Order

Place an order
Upgrade
Sales assistance
1-800-920-7713
Resellers
Licensing

Support

Request support
Frequently asked questions

Company

Profile
Products
Customers

I need recovery for... Use the product reference to locate a recovery solution for your application file, database, server or media.

Office and Windows

Email

Access

Exchange Server

Excel

Exchange OST

Money

Lotus Notes

QuickBooks

OneNote

PowerPoint

Outlook

Project

Outlook Express

Publisher

Undelete for Outlook

Word

Works

Windows Backup

Windows Registry

Servers

Databases

Active Directory

Access

BizTalk

FileMaker Pro

Exchange Server

Interbase / Firebird

Lotus Notes

MySQL

Project Server

Oracle

SharePoint

Paradox

PostgreSQL

SQL Server

Sybase

SQL Anywhere Server

Visual FoxPro

Other

Media

Zip

Flash Drive

PDF

Hard Drive

JPEG, GIF, TIFF, BMP, PNG or RAW

CD and DVD

Photo File

Diskette

Photoshop

Removable Disk

WordPerfect

Virtual Drive

Writer

Calc


No portion of this website may be reproduced without express written permission by Recoveronix
Copyright © 1998-2012 Recoveronix Ltd.