Product
|
Order
|
Support
|
Company
|
|
|
|
Recovery for SQL Server repairs corrupted SQL Server databases, backups and logs (.mdf, .ndf, .bak, .ldf). Supported SQL Server versions: Attention: make backup copies of corrupted file(s) before repair Click Repair 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.
Download a free demo version of Recovery for SQL Server.
The suite integrates multiple database repair utilities.
Is there an associated hardware problem or does the case need custom approach? Try our custom services.
New in Recovery for SQL Server 4.7:
Standard features:
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 repair 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 repair tool on both corrupted and healthy files.
Corrupted sql server databases are files that suddenly become unusable and can't be opened with Microsoft SQL Server. There are several reasons why a sql server file may have been damaged. In some cases, it is possible to fix and recover the corrupt mdf (SQL Server 2008 R2, 2008, 2008 x64, 2008 Express, 2005, 2005 x64, 2005 Express, 2000, 2000 x64, 7.0, 6.5), ndf, ldf, bak file.
If your mdf, ndf, ldf or bak database has accidentally become corrupt/inaccessible for opening with the original software, don't lose heart! OfficeRecovery represents you a new program, Recovery for SQL Server, that will help you to restore corrupted server databases. You can try to use the demo version of our program Recovery for SQL Server that allows you to evaluate the expected quality of a full recovery.
Use Cases can be used in situations when sql server file cannot be successfully opened in Microsoft SQL Server and you see errors or warnings while opening.
To repair corrupted mdf or bak file, try the demo version of Recovery for SQL Server.
It is important to note that if the restore process succeeds you will receive ready-to-use repaired sql server file as an output of recovery process. You can get fully repaired sql server database after the purchase by using the full version of Recovery for SQL Server.
Recovery for SQL Server can be ordered worldwide. Online credit card, phone, fax, mail/check and corporate purchase orders are accepted. Online orders are fulfilled in a few minutes 24 hours a day 7 days a week. Other types of orders are processed within one business day upon receipt.
All products are delivered electronically. Customer receives a receipt with download instructions by e-mail. Click link for desired license to begin ordering.
| 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 repair activity! |
| Q: | What limitations does the demo version of Recovery for SQL Server have? |
| A: | The demo version repairs 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 repair 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 repair 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 repair 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 repair. 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 repair my database information? |
| A: |
Recovery for SQL Server requires MDF file to repair database, backup and log. If you don't have an MDF, there's no way to restore your data. |
| 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 repair 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. |
I need repair for... Use the product reference to locate a repair solution for your application file, database, server or media.
|
|
|
No portion of this website may be reproduced without express written permission by OfficeRecovery
Copyright © 1998-2017 OfficeRecovery
