Recovery for SQL Server

Data fix software for corrupted Microsoft® SQL Server databases, backups and logs

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

Recovery for SQL Server Icon
Recovery for SQL Server
Recovery for SQL Server

Recovery for SQL Server repairs corrupted SQL Server databases, backups and logs (.mdf, .ndf, .bak, .ldf).

Supported SQL Server versions:
2008 R2, 2008, 2008 x64, 2008 Express, 2005, 2005 x64, 2005 Express, 2000, 2000 x64, 7.0 and 6.5

Attention: make backup copies of corrupted file(s) before fix

Click Fix to start

Version 4.7
Copyright © Recoveronix Ltd.

Recovery for SQL Server repairs corrupted SQL Server databases, backups and logs (.mdf, .ndf, .bak, .ldf).

Supported SQL Server versions:
2008 R2, 2008, 2008 x64, 2008 Express, 2005, 2005 x64, 2005 Express, 2000, 2000 x64, 7.0 and 6.5

The recovered data is saved into a set of SQL files to be used for rebuilding SQL Server database. This can be done manually or using an auto-generated rebuild batch file.

New major feature: view and selectively extract database, backup and log items using the Recovery for SQL Server Data Browser.

Free Demo

Download a free demo version of Recovery for SQL Server.

Related Products

DBRecovery 2010 Suite

The suite integrates multiple database fix utilities.

Data Recovery Services

Is there an associated hardware problem or does the case need custom approach? Try our custom services.


Features

New in Recovery for SQL Server 4.7:

Standard features:

Data Browser

Data Browser is a new feature bundled with the product, available from the same program group where Recovery for SQL Server is installed. It is a separate granular data fix utility to view and extract individual items from database, backup and log.

Always try the Data Browser if...

Tip: Recovery for SQL Server Data Browser can be used as a preview and fix tool on both corrupted and healthy files.

Limitations

System Requirements

Difference between demo and full version

The difference between demo and full version is only in "demo" values being recovered with full version. Except that, the demo and full versions are identical and comply with the same set of specifications. This means that if demo does not support a certain feature, neither full version will do.

If due to file damage an entire object (such as a table) has been lost, the full version will not be able to recover it. A table missing from a demo-recovered file will remain missing with full version.

Recovery Problems

Microsoft 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

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

Office and Windows

Email

Access (mdb, mda, accdb)

Exchange Server (edb, stm)

Excel (xls, xlsx, xla)

Exchange OST (pst)

Money (mny, mbf)

Lotus Notes (nsf)

QuickBooks (qbw, qba)

OneNote (one)

PowerPoint (ppt, pptx, pps)

Outlook (pst, ost)

Project (mpp)

Outlook Express (mbx, dbx)

Publisher (pub)

Undelete for Outlook (pst)

Word (doc, docx, rtf)

Works (wps, xlr, wdb)

Windows Backup (bkf, zip)

Windows Registry

Servers

Databases

Active Directory (dit)

Access (mdb, mda, accdb)

BizTalk (mdf)

FileMaker Pro (fp5, fp7)

Exchange Server (edb, stm)

Interbase / Firebird (gdb, fdb)

Lotus Notes (nsf)

MySQL (myd, myi)

Project Server (mdf)

Oracle (dbf, ora, dmp)

SharePoint (mdf)

Paradox (db)

VMWare (vhd, vmdk)

PostgreSQL

Virtual PC (vhd, vmdk)

SQL Server (mdf, ndf, bak, ldf)

Citrix Xen (xva, ova, img)

Sybase (dat)

Sun xVM (vhd, vmdk)

SQL Anywhere Server (db)

Visual FoxPro (dbf)

Other

Media

Zip

Flash Drive

PDF

Hard Drive

JPEG, GIF, TIFF, BMP, PNG or RAW

CD and DVD

Photo File (jpeg, tiff)

Diskette

Photoshop (psd, pdd)

Removable Disk

WordPerfect (wpd, rtf)

Virtual Drive (vhd, vmdk, ova)

Writer (odt)

Calc (ods)


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

recover sql server database | fix sql server file | repair sql server database