Available methods to repair Corrupt or Damaged SQL Server data files

-->

Sometime while opening SQL Server database files (MDF & NDF), Microsoft SQL server shows an error message that is “unable to open desired file because file is corrupt or damaged”. If you have maintained an updated backup for file then this problem will not have enough severity. But in case backup is not available anywhere of corrupt file, then you are left with only one option that is repairing of mdf or ndf files.

This post is all about how to repair corrupt SQL Server data files.

Repair Methods for corrupt MDF & NDF files: There are two methods to repair corrupt or damaged SQL server data file (MDF & NDF). Methods that I will describe in this post will be suitable for most of the SQL server version.

• Repair with DBCC CheckDB Utility
• Repair with Stellar SQL Recovery utility

Repair with DBCC CheckDB Utility: Microsoft SQL server offers an utility to repair corrupt SQL server that is DBCC CHECKDB. It has two options to repair corrupt file, repair-rebuild & repair-allow-data-loss.

• Repair-Rebuild: If level of corruption is less then DBCC CHECKDB will try to repair and rebuild your corrupt file with no data loss.

• Repair-allow-data-loss: In case level of corruption is very high then DBCC CHECKDB will try to repair your corrupt database file with minimum data loss. If your database is very critical and you can't afford any single data loss then go with second method.

Note: Your database should be in single user mode before running DBCC CHECKDB on database.

Repair with Stellar SQL Recovery Utility: Stellar SQL recovery utility is an robust tool to repair corrupt SQL server database files (MDF & NDF). It repairs tables, views, indexes, stored procedures, triggers, default constraints, primary keys, unique keys, foreign keys etc. You will have to perform some simple steps to repair your corrupt files by Stellar SQL recovery and the steps are....

Download-->Run-->Open Stellar Phoenix SQL recovery-->Choose your corrupt file-->Start scan-->See preview-->Start Repair-->Save Repaired File-->Done

You can see complete software details & working steps of Stellar Phoenix SQL recovery @

http://www.stellarsqldatabaserecovery.com/software-detail.php

 

http://www.stellarsqldatabaserecovery.com/screenshot.php

»»  Read More...

Repairing damaged MS SQL Server 2000 database by fixing Error 8943

Corruption in the SQL databases stops you from perform your usual tasks on the databases. Also, in some circumstances the database can become inaccessible as well. Such erroneous situations can arise due to various reasons like virus infections, database header corruption, abrupt or improper system shutdown, etc. To repair SQL database, you can use in-built corrective measures. If these measures are unable to bring normalcy to the database, then a good third-party SQL repair software should be used to do the needful.

Let us assume a situation in which you are getting the following error message while working on the MS SQL Server 2000 database:

“Table error: Object ID O_ID, index ID I_ID, page P_ID. Test (TEST) failed. Slot S_ID, row extends into free space at 0xADDRESS.”

Cause:

The root cause of this problem is that the end of the S_ID slot has crossed the permitted free space offset, ADDRESS.TEST is ‘max <= m_freeData’.

Here, the permitted free space offset is ‘m_freeData’ and the end of S_ID slot is ‘max’.

Resolution:

To overcome this issue, you should use the following methods ideally in the given sequence:

Check and resolve hardware-related errors: In most cases, these issues occur due to malfunctioning of the hardware components. You can check and resolve these issues using the following measures:

Checking the Windows Application logs and MS SQL Server error logs to see whether this error has occurred due to damaged hardware components.
Fixing the errors that appear after running hardware diagnostics.
Checking if the hard disk has write-caching enabled. If yes, then you should contact the local hardware vendor to get it replaced.
Reinstalling the operating system after formatting the hard disks.

Restore from backup: If the problem is not hardware-related, then you should check the state of the database backup. If it is clean and updated, then you should restore the database with its backup.

Run DBCC CHECKDB: You should run the DBCC CHECKDB tool to repair MDF file with the suggested repair clause.

If these methods are unable to provide solution for the damaged SQL database, then SQL repair can be done using a third-party MDF file repair software. These database repair tools are non-destructive in nature that do not modify the original database while repairing the damaged file.

The best MS SQL recovery software is Stellar Phoenix SQL Data Recovery, which repairs SQL databases created in MS SQL Server 7.0, 2000, 2005, and 2008 versions. Compatible with Windows 7, Server 2008, Vista, Server 2003, XP, and 2000, this .MDF repair software restores tables, NDF files, defaults, collations, stored procedures, etc.

Free Download SQL recovery software to see the preview of damaged/corrupted SQL Server database. This article is also posted on http://article-this.com/repairing-damaged-ms-sql-server-2000-database-by-fixing-error-8943/16907

»»  Read More...

Resolving Error 8925 in MS SQL Server 2000 database using SQL database recovery software

In MS SQL Server databases, the records are stored in the form of pages, which are linked to each other in a sequential manner. Because of being linked to each other, the searching and inserting new records is made easy thereby saving a lot of precious time. However, at times the database are unable to exhibit the expected functionality because of database corruption, which can occur due to various reasons such as virus infections, hardware malfunctioning, abrupt system shutdown, etc. In these circumstances, certain in-build methods can be used to recover SQL database. If these methods do not work, then I would suggest to use a third-party MS SQL Server software to overcome such situations.

Consider a situation in which you are getting the following error message while working on an MS SQL Server 2000 database:

"Table error: Cross object linkage: Page P_ID1, slot S_ID1, in object ID O_ID1, index ID I_ID1 refers to page P_ID2, slot S_ID2, in object ID O_ID2, index ID I_ID2."

Cause:

The primary cause of this problem is that the P_ID1 page points to another, P_ID2, page in a different object.

Resolution:

You should perform the following methods to recover MDF file in these situations:

* Address hardware-related issues: A lot of times these errors are caused by malfunctioning of the hardware components. You can use the following measures in order to resolve such issues:

o Fixing the errors that appear after running hardware diagnostics.
o Checking the Windows Application log report and MS SQL Server Error log to ascertain whether the error has occured because of hardware malfunctioning.
o Checking if write-caching is enaled on the disks. If yes, then contact the local hardware vendor to get it changed.
o Swapping the hardware components to isolate the actual reason of database corruption.
o Reinstalling the operating system after formatting the hard drive.

* Restore from backup: If the hardware is alright, then you should restore database from the backup if it is clean and updated.

* Run DBCC CHECKDB: If the backup does not solve the problem, then you should run DBCC CHECKDB with the suggested repair clause.

If you still are getting the similar error message even after using these methods, then you need to repair the damaged SQL database using a third-party master database file recovery software. These SQL database recovery tools are able to repair corrupt MDF files without any damage to the existing files.

The best SQL database recovery software that restores various database objects including collations, tables, NDF files, stored procedures, etc, is Stellar Phoenix SQL Data Recovery. Supporting MS SQL Server 7.0, 2000, 2005, and 2008, this .MDF recovery software is compatible with Windows 7, Server 2008, Vista, Server 2003, XP, and 2000.

»»  Read More...

Rectifying Error 5228 in SQL Server 2008

When you use the DML (Data Manipulation Language) commands to update the database, the rows sometimes get in an intermediate state. It is called the antimatter state that enables concurrent DELETE statements to leave a pointer for the index builder transaction so that deleted rows are not inserted again. Ideally, these rows should be deleted at the end of the operation. However, sometimes it does not happen that invariably results in database corruption. To resolve this situation, you should use appropriate corrective methods. However, if you are unable to do so then you should use a third-party MDF repair software to address the issue.

Consider a scenario wherein you are working on a table in SQL Server 2008. You get the following error message while performing some modifications on the database table:

“Table error: Object ID O_ID, index ID I_ID, partition ID PN_ID, alloc unit ID A_ID (type TYPE), page PG_ID, row R_ID. DBCC detected incomplete cleanup from an online index build operation. (Antimatter column value is VALUE.)”

Cause:

The root cause of this error message is that for the O_ID object , I_ID index, and PN_ID partition, there is an unfinished online index build was detected. This is testified by the presence and the displayed value of an antimatter column on the R_ID row.

Resolution:

To resolve this error message, you should perform the following methods, preferably in the given order:

Check for hardware issues: You should run the hardware diagnostics and check if the error appeared because of any hardware issue. You can also try to swap the hardware components to zero in and resolve the issue. In addition, you can try to reformat the disk and reinstall the operating system.


Restore from backup: Check if you have a clean and updated backup of the database. If yes, then you should restore the database with its backup.

Run DBCC CHECKDB: As a last resort, you should run the DBCC CHECKDB command without the repair clause to ascertain the level of the corruption. You should run the command again after knowing the repair clause. It will rebuild the corrupted indexes.

However, if you still are not able to resolve this error by any which method then you should use a third-party SQL recovery software. Such read-only tools are able to recover SQL database using sophisticated scanning algorithms without overwriting the original data.

Stellar Phoenix SQL Recovery is an MS SQL recovery software that enables you to recover corrupted databases created in SQL Server 2000, 2005, and 2008. It is competent enough to restore various objects of SQL database such as tables, queries, stored procedures, triggers, views, etc. This SQL recovery software is also able to preserve the database constraints and user-defined data types. It is compatible with Windows 7, Vista, Server 2003, XP, and Server 2000.

»»  Read More...