'SQL Database Recovery | Repair SQL Database' Blog RSS Feed

Powerful MS SQL repair software to repair and recover your corrupt SQL database

markwillium — Wed, 16 Feb 2011 03:29:51 -0800

Sometimes, while working in Microsoft SQL, it issues warning messages. A possible database corruption is the reason behind such alarming messages. Though many users ignore such messages and start experimenting with the database, which results in harsher instance of data loss or inaccessibility. Therefore, when your valuable data is lying in the database, handle it with extreme care and it would be wise to use any reliable SQL repair utility to repair the database and recover the data back.

After encountering the error or warning message, which gets flashed every time you try to open the database, the tables in the MS SQL database becomes completely inaccessible. Moreover, repeated occurrence of the error may result in more complex corruption of the SQL database. The error message that you may have come around can be as read as below:

Warning: Page P_ID, slot S_ID in Object O_ID Index I_ID Column COLUMN_NAME value COLUMN_VALUE is out of range for data type "DATATYPE". Update column to a legal value.

Cause:
The above error message tells that the particular column contains an illegal value, which can be caused by any logical or physical corruption of the SQL database.

Resolution:
In order to resolve the above case of database corruption and recover the data back from it, you have to run the command ‘DBCC CHECKDB’ with the recommended repair clause.

However, with severe corruption, this command fails to repair the database and you need to restore the database from any previously created valid backup. But, if you do not have any valid backup available, still you can recover the data by repairing SQL database with the help of any mdf repair software.

These MS SQL repair utilities are innovatively developed applications to successfully repair the SQL database and recover all the data from it. These applications are absolutely read-only in nature and recover database keeping the integrity intact. Moreover, with highly interactive and easy-to-use user interface, any user even without much technical knowledge can use the software and repair SQL database.

Stellar Phoenix SQL Recovery is a heavily used and highly appreciated SQL server recovery utility for its safe and efficient recovery of data from any instance of database corruption. The software is compatible with SQL Server 2008, 2005, 2000 and recovers the database tables, containers, schema, stored procedures etc without even altering their original format. Above all, this wonderful utility incorporates absolutely easy-to-use functionalities and provides a lucid recovery experience.

How to Resolve Error 5171 in Microsoft SQL Server Database

markwillium — Sun, 06 Feb 2011 22:35:06 -0800

Most of the companies use Microsoft SQL server database for storing their database where database administrator handle all the issue for maintaining the database by the use appropriate SQL server commands. Microsoft SQL server database may be corrupted by Improper system shutdown, hardware failure, SQL Server malfunctioning, virus infection, hardware failure and many more. Once SQL server database gets damaged, the data stored in the SQL Server become inaccessible. In such scenarios, use latest and updated backup, if backup is not updated, then database administrator needs to used a third party SQL recovery software to repair mdf file.

Consider a situation, wherein a database administrator is working on SQL Server database and creating a report. While doing this, the Windows automatically restarts due to power failure. When database administrator restart the system, the SQL server database becomes inaccessible. When the database administrator tries to attach MDF manually, he encounters the given below error message:

“An exception occurred while executing a Transact-SQL statement or batch. _db.mdf is not a primary database file. (Microsoft SQL Server, Error: 5171).”

Or

“C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\MYDATABASE.mdf is not a primary database file. (Microsoft SQL Server, Error: 5171)”

In such situations, most the database expert recommend to attach a single file. However, when the database administrator uses sp_attach_single_db Stored Procedures, the database administrator encounters the given below error message:

“Server: Msg 5172, Level 16, State 15, Line 1 The header for file path……\.mdf is not a valid database file header. The PageAudit property is incorrect.”

The above problem generally occurs when the Master database file header gets damaged/corrupted or some invalid value is inserted in the master database header file. All of these situations became, inaccessibility of the SQL server database. To accessibility of the SQL server database, the database administrator needs to recover mdf by using the updated backup. But sometime database administrator has not created any backup of its SQL server database, then he needs to perform MDF file repair. To do so, database administrator needs to use an effective and efficient SQL recovery application.

Most of the database experts recommend Stellar Phoenix SQL Recovery software to repair the corrupted mdf file. This software uses an advanced scanning algorithm to repair and recover corrupted mdf file. It is compatible with SQL server 2008, 2005, 2000, and 7.0

How to perform SQL database recovery in case of MS SQL Server Error 9004

markwillium — Thu, 27 Jan 2011 03:36:28 -0800

A transaction log is an important component of database which is often ignored or overlooked as it is not regularly maintained or used by the database administrators or users. It keeps track of all the changes made to the database and maintains a separate data file to store the actual data. Transaction log backup and the corresponding data file backup can be used to perform database recovery in case of a corruption and restore the database to its original state. But the transaction log may get corrupt due to several reasons, such as installing wrong drivers, virus attack, hard drive failure, system table corruption etc. In such situations, the transaction log may become inaccessible and thus, you may not be able to restore your database. To overcome this problem, you need to go for SQL database recovery through a reliable third party utility.

While trying to access a corrupt transaction log, you may see the following error in ERRORLOG or Windows Application Event Log:

"Error: 9004, Severity: 21, State: 1.

An error occurred while processing the log for database 'mydb'. If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log."

Cause:

This error may have occurred due to any of the following reasons-

The file system is corrupt.
A hardware error
Damaged drivers
SQL Server Engine problem

The transaction log corruption may also lead to a corrupt database. To recover back your lost data in case of any corruption scenario, you need perform SQL recovery by following below mentioned resolution steps.

Resolution:

Try to restore the transaction log from a backup. If you are unable to recover it from a backup, you may try to rebuild the log and bring it on-line.

Rebuilding of the transaction log should be done carefully as it can result in transactional consistency loss in the database. In all these circumstances, you should take help of a reliable database recovery software in order to recover back your lost valuable data from the corrupt database. These software are capable of repairing those database files as well that are not repaired by the DBCC CHECKDB tool.

Stellar Phoenix MSSQL Database Recovery Software is a recovery utility that repairs and restores MS SQL Server databases from all scenarios of corruption. It supports MS SQL Server 7.0, 2000, 2005, and 2008. It can recover all database components including tables, views, rules, user defined functions, indexes, constraints etc. It performs SQL repair by allowing you to search for the corrupt MDF file in your system.

Resolving Table Error - Object Id O-ID - Possible Bad Root Entry in Sysindexes

markwillium — Mon, 24 Jan 2011 04:30:50 -0800

The metadata structure of SQL Server database comprises of numerous Index pages, which further consist of data pages. The data pages at each level of Index page are linked in a doubly-linked list. Inaccessibility of data stored in the data pages primarily occurs due to breaking of linked list (metadata structure corruption). Additionally, it also results in unmountability of the database. Few main reasons for metadata structure damage are improper system shutdown, virus hits, or physical damage. An easy solution to overcome the metadata structure corruption situation, you will need to restore the data from an updated database backup. However, with case studies proving that database users tend to forget to create an updated database backup, it is always handy to take help of third-party sql database repair applications.

Picture a scenario, where you receive the below error message while you attempt to mount your SQL Server database:

"Table error: Object ID O_ID, index ID I_ID. Page P_ID1 is missing references from parent (unknown) and previous (pageP_ID2) nodes. Possible bad root entry in sysindexes."

The result of the above error message is unmountability of your database, which further results in inaccessibility of database records.

Cause

The root cause for the occurrence of above error message is not linking of P_ID1 to the B-tree. The message can be caused either due to hardware or software issues.

Resolution

To resolve the above error message and to access the database records, you will need to follow the below steps:

Change the physically damaged system component with a new system component to resolve all physical damage problems.

Execute DBCC CHECKDB command to resolve logical corruption issues.

While the former resolution proves successful in resolving all physical corruption scenarios, the later fails to resolve all logical corruption issues. For resolving every logical corruption problem, you will need to use advanced SQL Database Repair software. These sql recovery tools repair corrupt SQL database by using advanced scanning and repairing algorithms. Additionally, these applications perform repair without deleting or modifying the original content of the database.

SQL Recovery comprehensively repairs and restores database created in SQL Server 2008, 2005, and 2000 versions. The sql database repair software is designed for Windows 7, Vista, XP, 2003, 2000 and NT operating systems. It repairs almost all database objects, including tables, stored procedures and views, and supports.

How to Rectify Consistency Errors in System Catalog

markwillium — Tue, 18 Jan 2011 04:56:46 -0800

System catalog is a group of tables that database management system itself creates and maintains user-defined objects such as tables, schemas, domains, constraints, other catalogs, security and many more in the database. Tables in the system catalog are known as the system tables because they contain data that describe the structure of the database. Sometimes tables of the SQL Server database get corrupted due to several reasons like virus attach, system failure, power outages, etc. In such cases you should use proper method to rectify the problem. If you are not able to repair your SQL Server database then used as advanced third party SQL Server recovery software to fix the problem.

Consider a praticle scenario where you may encounter the given below error message while using the DBCC CHECKNAME command on SQL Server database:

"Database 'DBNAME': consistency errors in system catalogs prevent further DBCC CHECKNAME processing."

Cause of problem:

There are several possible cause of above error message, some of them are given below:

The System base tables are damaged or corrupt.

The System base tables store the metadata for the all objects in the database.

Resolution:

For resolving above error messages, you have to do some steps which is given below:

Resolve hardware issue: You should check the error log and hardware component. If you will find any problem with the hardware then replace it with the new one.

Restore from Backup: After you have satisfy from the harware and still unable to recover database then restore the SQL Server database from latest backup and fix the problem.

Run DBCC CHECKDB Command: If your backup is not clean and updated the run DBCC CHECKDB command to resolve the problem.

After completing all the above steps in given order and still unable to access SQL server database then you should try an advanced SQL recovery tool to recover sql server database.

Stellar Phoenix SQL Recovery is an advanced sql recovery tool that repairs SQL databases from all instances of logical corruption. It is specifically designed to perform MS SQL recovery for databases created in SQL server 2008, 2005, 2000, and 7.0.

System Table Corruption Causes Data Loss in SQL Server

markwillium — Mon, 17 Jan 2011 05:30:53 -0800

Microsoft SQL Server is a reliable and advanced database management system that provides you various database management and SQL database recovery algorithms. DBCC CHECKDB is one of the most advanced SQL Server commands that helps you repair corrupt database. However under some situations, this command fails with an error and cannot repair damaged database. This behavior leads to critical data loss and requires SQL Server recovery to be fixed.

DBCC CHECKDB command may not recover SQL Server database due to various reasons, such as metadata structure corruption, system table damage, and faulty database index. For instance, consider the following error message that occurs when you try to perform MS SQL recovery using DBCC CHECKDB command-

"Database MyDB: Check Data and Index Linkage...

Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 8921: [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKTABLE terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is corrupt. Check previous errors.

Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 1 consistency errors not associated with any single object.

Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 1 consistency errors in database 'MyDB'.

Microsoft][ODBC SQL Server Driver][SQL Server]repair_fast is the minimum repair level for the errors found by DBCC CHECKDB (MyDB )."

The above error occurs with every parameter of DBCC CHECKDB command, including REPAIR_FAST.

Since the database remains corrupt due to DBCC CHECKDB failure, its records also remain inaccessible.

Cause:

You may encounter this problem if SQL Server database or MDF file has severe logical corruption. DBCC CHECKDB command cannot handle serious corruption and perform MDF recovery.

Solution:

In order to sort out this problem and extract your precious data from inaccessible data, go through the below SQL recovery steps-

Restore MDF file from an updated and valid backup.

If backup is not current, use commercial MS SQL repair software to ensure absolute MDF file recovery.

Such efficient SQL database recovery applications are particularly designed to repair MDF file using advanced SQL recovery algorithms. The MDF recovery software do not demand sound technical skills to repair SQL database as of their interactive MS SQL recovery user interface.

You need not to worry about integrity of your database as MS SQL recovery applications perform safe recovery with read-only conduct. You can use free demo version of these applications to check out their features and functionalities.

Stellar Phoenix SQL Recovery software helps you perform SQL Database recovery for Microsoft SQL Server 2008, 2005, 2000, and 7.0.

How to overcome Error 8921 in MS SQL Server 2000 database

markwillium — Thu, 23 Dec 2010 04:42:13 -0800

In MS SQL Server, the CHECKTABLE command is used to check the integrity of the database tables. To do this, it uses several parameters to perform different types of checks. However, if the table is corrupt then this command may not work and exit abruptly. Such database corruption may cause because of several issues including virus infections, hardware malfunctioning, etc. These cases can well be solved using appropriate corrective measures failing which you should use a third-party MS SQL repair software to do the needful.

Consider a scenario in which you are running the CHECKTABLE tool on a database in MS SQL Server 2000. However, the tool fails to execute and exits abruptly showing the following error message.

"CHECKTABLE terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors."

Cause:

The reason behind the failing of CHECKTABLE is that the internal query that DBCC uses to acquire parallelism and scalability due to some miscellaneous reason such as database corruption.

Resolution:

The database corruption can be handled using the following MDF repair methods:

Address hardware corruption issues: You should check if the issues is not being caused due to hardware malfunctioning. You can use the following measures to find out and resolve such issues:

Running hardware diagnostics and fixing any errors that occur while doing so.
Checking Windows application log and MS SQL Server Error log to see whether some error has appeared because of hardware corruption. Try to correct the problem, if possible.
Swapping the hardware components to try and isolate the exact reason of database corruption.
Reinstalling the operating system after formatting the hard disks.

Restore from backup: If the hardware components are perfectly in place, then you should check the state of the database backup. If the backup is clean and updated, then you can restore the database from the backup.

Run DBCC CHECKDB: If the backup solution is not possible, then run DBCC CHECKDB with the appropriate repair clause to repair MDF file.

If the aforementioned methods are unable to resolve the issue, then you should use a third-party MDF file repair software. These database repair tools are extremely safe to use that do not damage the existing while performing SQL repair.

The best SQL database recovery tool that repairs SQL database in most occasions is Stellar Phoenix SQL Data Recovery in MS SQL Server 2008, 2005, 2000, and 7.0. Able to recover various SQL objects including collations, NDF files, tables, stored procedures, triggers, etc, this .MDF repair software is compatible with Windows 7, Server 2008, Vista, Server 2003, XP, and 2000.

Resource taken from here: http://goarticles.com/article/How-to-overcome-Error-8921-in-MS-SQL-Server-2000-database/3838582

Using professional MySQL recovery tool to solve table corruption in MySQL database

markwillium — Fri, 17 Dec 2010 04:22:18 -0800

The MySQL database is extensively used as part of the LAMP (Linux, Apache, MySQL, and PHP/Python/Perl) stack. All these applications are very popular because these are freely available, fast, very reliable and secure. For these reasons the applications made on the LAMP stack are hugely preferred for the Web-based applications. But as they say, nothing is perfect in this world. These applications too can get stuck because of table corruption in MySQL databases thereby making all the concerned data inaccessible and insecure. Such instances can appear because of various causes such as abrupt system shutdown, virus infections, file header corruption, etc. You can try out several table repair methods to fix the problem. If you do not succeed in MySQL recovery, then the best option is to use a third-party MySQL repair software.

To relate with this matter, consider a scenario in which you are working on a MySQL table. In this, you try to run a query but it fails to execute. The following error message is displayed after this problem happens:

"MySQL server has gone away"

Cause:

The main causes of this problem are:

The MySQL connection is closed because of server time out.

The query is too large or complex to execute.

You are trying to run the query on the closed connection.

The connection on the client side is closed.

The MySQL table is corrupt.

Resolution:

You can perform the following methods to fix the problem:

Try to establish the connection again with the server and try that query again to ensure whether this is a server-related problem.

Run Optimize Table command. If it shows the following error message, then you should perform the steps given after the error message:

ERROR 1030 (HY000): Got error 28 from storage engine

Add the following line to the my.cnf file:

innodb_force_recovery=4

Stop the MySQL server and restore the backup to the "mysql" folder.

Now restart the MySQL server and try that query again.

It should work fine now.

Well, if the query does not work even now, then there must be a more serious corruption with the MySQL table. In such cases, I would suggest you to take the services of a third-party MySQL repair software to repair MySQL database. These tools use non-destructive algorithms to safely recover MySQL database.

One such efficient tool is Stellar Phoenix Database Recovery for MySQL that repairs various types of MySQL database files. Designed to support MyISAM and InnoDB database engines, this MySQL recovery tool is compatible with Windows 7, Vista, Server 2003, XP, and 2000.

About The Author:

My name is Mark Willium, I have done Ph.D in computer science and currently doing research on how to recover and repair corrupted MySQL database. You can have more information about MySQL database recovery tool by visiting here http://mysql-database-recovery.blogspot.com/

Recover Master File from SQL Server database by SQL Recovery Software

markwillium — Wed, 08 Dec 2010 04:05:56 -0800

Structured query language (SQL) is a database computer language designed for managing data in RDBMs developed by Microsoft corporation. It has two primary query languages, ANSISQL and T-SQL. It offers the facility to access SQL Server database from anywhere, be it from your desktop or data center. It also provides combined services to search, query, report synchronize and analyze the database records. Sometimes it may happen that the SQL Server is unable to run. It may possible that the master database of SQL Server has gone damaged. This can be possible because of several reasons such as human errors, virus infections, power outages while SQL Server was open. In that case, you should replace the damaged database with its clean and backup. However, if the backup is not clean and updated then you should use an advanced sql recovery software to recover SQL database.

Consider a case wherein you have Microsot SQL Server installed on your machine. When you try to log on to the SQL Server, you are unable to do and an error message is appered, that is:

"Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online."

Cause:

The possible cause for the above mentioned error message is that the SQL Server database is unable to start the master database. If the tempdb or master database can not be mounted, SQL Server can not run. It is possible that the master database of SQL Server has gone damaged because of various above mentioned reasons.

Resolution:

To solve the above issue, you should first of all, check there is a clean and updated backup of the master database. If yes, then you should replace updated backup with the damaged master database. However, if the database is not clean and updated then you should use a SQL repair tool to perform sql recovery of the damaged master database.

Stellar SQL Database Recovery software is an advanced SQL Recovery tool that repairs and restores corrupted mdf as well ndf files of SQL Server database. This software is able to repair various database components such as tables, stored procedure, defaults, triggers, rules, and views. It is compatible with Windows 7, Vista, Server 2003, XP, and 2000.

Repairing Corrupt SQL Database in MS SQL Server 2000 in Case of Error 8946

markwillium — Fri, 03 Dec 2010 05:21:31 -0800

A page header in a database page is the first 24-bytes of the page that contains the general information about the page such as the details about the free space pointers. It is, thus, a significant part of the database page, which can pose problems if it gets damaged. The page header damage is possible in different circumstances such as virus infections, unplanned system shutdown when the database is open, power outages, etc. In such cases, you should repair SQL database using appropriate corrective measures. However, if these methods do not work for the database then you should use a third-party MS SQL repair software to perform SQL database recovery.

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

"Table error: Allocation page P_ID has invalid PAGE_TYPE page header values. Type is TYPE. Check type, object ID and page ID on the page."

Cause:

The most possible cause of this problem is that the specified page has an invalid page header, which is raising the mentioned error.

Resolution:

To overcome this problem, you should perform the following methods, preferably in the given sequence:

Addressing the hardware-related issues: Lot of times, such errors are caused due to database corruption due to hardware malfunctioning. You can fix these issues using the following measures:

Fixing the errors that come up after running hardware diagnostics

Checking the Application logs and SQL Server error logs to check if the error has occurred due to hardware corruption.

Swapping the hardware components to isolate the actual reason of corruption.

Installing the operating system after formatting the hard disks to get a fresh system.

Using backup of the damaged database: If the hardware is perfectly in place, then check the status of the database backup. If it is updated and clean, then restore the database using the backup.

Running DBCC CHECKDB: If the previous method does not solve the problem, then you should repair MDF file using DBCC CHECKDB utility with the recommended repair clause.

If you still are not able to fix the error, then you should use a third-party MS SQL repair software to repair the damaged database. These MDF file repair tools use fast and sophisticated scanning mechanisms to repair SQL database without overwriting the existing database.

The most recommended SQL recovery software that recover SQL databases created in MS SQL Server 2008, 2005, 2000, and 7.0, is Stellar SQL Recovery. With the capability to repair SQL databases to recover tables, collations, NDF files, defaults, triggers, etc, this .MDF repair software is compatible with Windows 7, Server 2008, Vista, Server 2003, XP, and 2000.

Source: http://www.americanchronicle.com/articles/view/201617

Fixing Error 8947 by recovering damaged MS SQL Server 2000 database

markwillium — Thu, 02 Dec 2010 04:18:19 -0800

An IAM (Index Allocation Map) is a page in the database that stores one bit per extent in all the GAM (Global Index Map). A set bit is used to point out that the extent is allocated to that particular index. At times, this convention is not followed as two IAM pages refer to the same GAM interval. Lot of times, this problem is caused due to database corruption, which in turn, can occur because of virus infections, database header corruption, abrupt or unplanned system shutdown, etc. There are several methods that can be used to achieve MDF file recovery. However, if you fail to do so then you should use a third-party SQL recovery software 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: Multiple IAM pages for object ID O_ID, index ID I_ID contain allocations for the same interval. IAM pages P_ID1 and P_ID2.”

Cause:

The root problem of this error is that the IAM chain for the specified index has two IAM pages, P_ID1 and P_ID2, that cover the same GAM interval.

Resolution:

To overcome from such situation, you should perform the following methods, preferably in the given order:

Addressing the hardware-related problems: First of all, you should look at the hardware-related issues that may have caused the database corruption. Some of the measures that you can follow are:

Checking if write-caching is enabled on the hard disks. If yes, then you should get the hard disk replaced from your local hardware vendor.

Fixing any error that appear after you run hardware diagnostics.

Checking the Application error logs to ensure that the problem is not caused from hardware malfunctioning.

swapping the hardware components to isolate the actual error of corruption.

Restoring from backup: You should check the status of the backup. If it is clean and updated, then you should restore the database with the backup.

Running DBCC CHECKDB: You should repair SQL database using DBCC CHECKDB tool with the suggested repair clause.

If you still get the same error, then you should recover MDF file with the help of a third-party SQL database recovery software. These tools use highly advances scanning mechanisms to safely recover database without any modifications.

The MS SQL Server recovery software that is recommended by most recovery experts is Stellar Phoenix SQL Data Recovery, which recovers SQL databases created in MS SQL Server 2008, 2005, 2000, and 7.0 versions. Recovering tables, stored procedures, NDF files, collations, defaults, etc, this master database file recovery software is compatible with Windows 7, Sever 2008, Vista, Server 2003, XP, and 2000.

Referrence: http://article-this.com/fixing-error-8947-by-recovering-damaged-ms-sql-server-2000-database/15797

Tips to Resolve "Page %s-pgid is Allocated" Error Message

markwillium — Mon, 22 Nov 2010 03:58:18 -0800

DBCC CHECKALLOC is a common command that is used by database users to check the consistency of disk space allocation. The command comprehensively examines the use and allocation of all pages in your specified database. However, if examining the pages, the command displays an error message, then it means that your database pages have been corrupted or damaged. Furthermore, the data stored in the database becomes inaccessible after the error message appears. An ideal way to access your data in such situations is by restoring the data from an updated backup. But if in case, your database backup has been corrupted or damaged, then you will need to use advance SQL Repair application to repair your database.

As a practical instance, you encounter the below error message when you run DBCC CHECKALLOC command:

"Table error: Page %S_PGID is allocated to object ID %d, index ID %d, not to object ID %d, index ID %d found in page header."

After the above error message appears, the data stored in the database becomes inaccessible.

Cause

The root cause for the occurrence of the above error message is that DBCC CHECKALLOC statement has detected a mismatch in the Object ID between sysindexes and extents. This primarily occurs due to metadata structure corruption.

Resolution

To resolve the above error message, you will need to follow the below mentioned underneath steps:

1.Check the index ID connected with the page number highlighted in the error message to find the error occurred on the index or on table data.

2.Next, restore the database after analyzing the underneath situations:
If the Object ID in the error message contains a value less than or equal to 100, then the system table is corrupted. In such situations, restore the database from a clean backup.
In case, the value is greater than 100, the error is in user table. Restore only the table in such situations.
If the index ID contains a value equal to 1, then you will need to restore the database from an updated backup.

However, if the above steps fail to resolve your issue and the error message still persists, then you will need to use advanced third-party sql repair software to access your database. Such SQL Database Repair applications provide comprehensive database repair by using powerful scanning methods.

SQL Recovery is an impressive sql database repair tool to repair damaged SQL Server 2008, 2005, and 2000 databases after all kinds of logical crash. The read only software provides risk-free recovery of lost components by storing them on a new database file, leaving the original database file untouched.

Adishree Singh work as a freelancer and researcher repair sql & database repair software software. This tool helps to damaged SQL Server 2008, 2005, and 2000 databases after all kinds of logical crash.

Article Source: http://EzineArticles.com/?expert=Adishree_Singh

Table Error Post Metadata Structure Corruption

markwillium — Mon, 15 Nov 2010 04:41:28 -0800

MS SQL Server database is build up of various metadata structure components like, pages, extent, etc. Pages are the smallest unit of data storage that store actual data. A combination of 8 adjacent pages makes an Extent. Corruption or damage in metadata structure primarily results in inaccessibility of records stored in your database. In most of the database corruption situation, you encounter an error message stating the cause for the error. For successful access of records stored in your database and overcoming hazards created by error message, an easy way is to restore the database records from an updated backup. But if in case, your backup file has been corrupted, damaged, or unreadable, then you will need to use advanced repair software that can comprehensively repair MDF files.

Consider a practical case, where you encounter the below error message when you attempt to access the records stored in your MS SQL Server database:

"Table error: Extent P_ID object ID O_ID, index ID I_ID is beyond the range of this database."

The above table error message primarily results in inaccessibility of records stored in your database. Furthermore, the error message reappears each time you attempt to access the database.

Cause:

The fundamental reason for the occurrence of the above error message is corruption of metadata structure (in this case, Extents). Extent corruption can occur due to various reasons, such as, improper system shutdown, virus attack, human error, and more. Te corruption can also occur due to various physical damages in your hard drive, like accidental dropping of hard drive, natural disasters, power spikes, and more.

Resolution:

To stop the error message from occurring and to make your records accessible, you will need to use follow underneath steps:

In case of metadata structure corruption due physical crash of hardware, change the old hardware with new one.
For metadata structure corruption caused due to logical crashes, run DBCC CHECKDB command (with recommended repair clause).

After using the above measures, there is a very dim possibility for popping of above error message. However, if it does, you will need to use a powerful mdf repair software to repair your database. These MDF Repair tools are extremely user-friendly as they are built with highly graphical user-interface.

Stellar Phoenix SQL Recovery is a fantastic application to repair mdf file corrupted after any logical crash. The software supports SQL Server 2008, 2005, and 2000 and provides access to all your lost database components, such as, views, triggers, stored procedures, etc.

Adishree Singh work as a freelancer and researcher repair sql & sql repair software.

Article Source: http://EzineArticles.com/?expert=Adishree_Singh

Fixing "Table Error: ... offset 0xADDRESS overlaps with the prior row" Error

markwillium — Tue, 09 Nov 2010 04:51:18 -0800

You must have encountered the table error messages while accessing the MS SQL Server database tables. These errors occur because of some integrity issues in the database tables. Sometimes, the integrity issues can take place because of having a corrupt database. And a database can get corrupted because of various internal and external issues such as virus attacks, human errors like improper system shutdown especially when the database is open, sudden power fluctuations, data integrity issues due to mishandling the database such as changing the structure of the database, multiple users trying to change the database table simultaneously, etc. Because of the table errors you can face various problems such as partially or completely inaccessible database, retrieving corrupt records, regularly displaying error and warning messages, and so on. These problems are bound to pose serious threats especially when you are working on a real-time environment. To counter such situations, you can restore the database by overwriting it with its updated backup. However, if the backup is not the updated one then you will have to use the advanced SQL Database Recovery application to repair the corrupt database.

Consider a practical situation wherein you have created a table called "Accounts" in a database. However, when you open the table the following error message is displayed:

"Table error: Object ID O_ID, index ID I_ID, page P_ID. Test (TEST) failed. Slot S_ID, offset 0xADDRESS overlaps with the prior row."

The records in the "Accounts" table become inaccessible once the aforementioned message is displayed.

Cause:

The aforementioned error message occurs when the offset of the S_ID slot is not equal to or greater than the end of the previous slot. And the reason for this is that there is a 'test' table in which the value of the sorted[i].offset is not equal to or greater than the expected value.

Resolution:

To address the mentioned error and in turn, successfully access the "Accounts" table, you can perform the following methods:

Check the SQL Server Error Log to find out if there is any hardware issues that is causing this problem. If it is so, replace the damaged hardware. If it is not a hardware issue, then you need to run the DBCC CHECKDB command without using any repair clause. This way, you can find out the exact repair clause that needs to be applied for the database repair. Then, you can run the DBCC CHECKDB command with that repair clause. However, performing the previous method can result in data loss. So, to avoid any data loss you should take the help of a sophisticated SQL Repair tool. These tools use safe and robust algorithms to repair almost all kinds of corrupt database components.

The Stellar SQL Database Recovery tool recovers and repairs the SQL tables and other components in three steps. The SQL Database Repair tool can be used to recover database components created in MS SQL Server 2008, MS SQL Server 2005, and MS SQL Server 2000. The recovery tool is compatible with various Windows operating systems such as Windows 7, Windows Vista, Windows XP, Windows NT, etc.

About the Author

My name is Mark Willium, I have done Ph.D in computer science and currently doing research on how to recover and repair corrupted SQL database.

How to repair Error 8926 in a corrupt MS SQL Server database

markwillium — Thu, 28 Oct 2010 03:40:54 -0800

Are you facing problems while working on a particular MS SQL Server 2000 database? If yes, then you should see if the same problem is reproducing on other databases as well. If not, then there are very strong chances that the database is corrupt. It could have become corrupt owing to miscellaneous reasons such as virus infections, malfunctioning of the hardware components, abrupt system shutdown while the database is open, etc. In such cases, you should fix the error by repairing SQL database failing which you should use a third-partySQL repair software.

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

"Table error: Cross object linkage: Parent page P_ID1, slot S_ID1 in object ID O_ID1, index ID I_ID1, and page P_ID2, slot S_ID2 in object ID O_ID2, index ID I_ID2, next refer to page P_ID3 but are not in the same object."

Cause:

The problem in this case is due to the corruption in the page definitions in the SQL database.

The next page pointers of P_ID1 and P_ID2 pages are pointing each other in an incorrect manner leading to the error.

Resolution:

To address this problem, you would need to repair MDF file. To do this, you shold perform the follwoing methods preferably in the given order:

Fix hardware related issues: As is seen in many instances, such errors occur due to hardware malfunctioning. This can be addressed using the following measures:

Run the hardware diagnostics and try to repair the errors that you

Check the Windows Application log and MS SQL Server Error log to see whether the error has occurred because of any hardware-related problem.

Swap the hardware components to check and find out the exact reason for corruption.

If nothing else works out, then you can reinstall the operating system after formatting the hard disks.

Restore from backup: If the issues is not hardware-related, then you should restore the database from its clean and updated backup.

Run DBCC CHECKDB: In the end, you can choose to repair SQL database using the DBCC CHECKDB command using the appropriate repair clause.

If the problem is persisting, then you should repair the damaged SQL database using a third-party MDF file repair software. These read-only tools are able to repair and restore SQL components without inflicting any damages to the original database file.

The .MDF repair software that is recommended by most of the database recovery experts is Stellar Phoenix SQL Data Recovery. Able to recover SQL databases created in MS SQL Server 7.0, 2000, 2005, and 2008, this MS SQL repair software restores tables, NDF files, stored procedures, triggers, etc. In addition, this software is compatible with Windows 7, Server 2008, Vista, Server 2003, XP, and 2000.

My name is Mark Willium, I have done Ph.D in computer science and currently doing research on how to recover and repair corrupted SQL database.

How to recover MDF file when you encounter Error 8910 in MS SQL Server 2000

markwillium — Wed, 27 Oct 2010 03:42:58 -0800

Are you getting error messages repeatedly while working on a particular database in MS SQL Server 2000? If yes, then you should check the exact cause of these messages as there may be chances of database corruption. The database corruption can happen due to various reasons including virus infections, malfunctioning of the hardware components, abrupt or unplanned system shutdown while the database is open, etc, which could even make the database inaccessibile. In such cases, you should look for MDF file recovery using appropriate corrective methods, failing which you must use a third-party MS SQL Server recovery software to do the needful.

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

"Page P_ID in database ID DB_ID is allocated to both object ID O_ID1, index ID I_ID1, and object ID O_ID2, index ID I_ID2."

Cause:

The most prominent reason behind this error is that the index definitions in the IAM pages have damaged.

Resolution:

To perform MDF recovery of the damaged SQL database, you should perform either of the following methods, ideally in the given sequence:

Address hardware related issues: It may be possible that the error is occurring due to hardware corruption, which can be resolved using the following measures:

Fixing the issues that appear after running hardware diagnostics.
Swapping the hardware components to isolate the exact reason and fixing it.
Checking the Windows application log and the SQL Server error log to find out whether the error has occurred due to hardware malfunctioning.
Checking if the hard disk has write-caching enabled. If yes, then contact the hardware vendor to replace the hard disk.

Restore from database: You should check the state of the database backup. If it is updated and clean, then you should restore the database with its backup.

Run DBCC CHECKDB: If the backup is not clean, then you should run the DBCC CHECKDB tool with the suggested repair clause to recover MDF file.

If these aforementioned methods are unable to address the situation, then you would need to take the services of a third-party master database file recovery software. With the use of read-only recovery mechanisms, these SQL recovery tools ensure that no type of data is lost or damaged during the recovery.

In such cases, I would recommend you to use Stellar Phoenix SQL Data Recovery, which recovers SQL databases created in MS SQL Server 7.0, 2000, 2005, and 2008. Performing .MDF recovery by recovering databases components including NDF files, stored procedures, tables, defaults, triggers, etc, this SQL database recovery software is compatible with Windows 7, Server 2008, Vista, Server 2003, XP, and 2000.

How Would You Fix the Error 8928 to Repair Damaged Database in MS SQL Server 2000?

markwillium — Tue, 26 Oct 2010 03:45:13 -0800

The PFS (Page Free Space) pages in the MS SQL Server databases are used to search for free space in the database tables. It holds a byte-map which contains one byte per page that is represented by P_ID. Sometimes, you are unable to read the PFS page that can happen due to database corruption. The corruption cases are caused due to various issues such as abrupt or improper system shutdown when the database is open, virus infections, etc. In such circumstances, you should try to recover SQL database using appropriate methods. If you are unable to workaround the issue, then you should use a third-party SQL database recovery software to address the problem.

Consider a scenario wherein you are facing the following error message while working on an MS SQL Server 2000 database:

"Object ID O_ID, index ID I_ID: Page P_ID could not be processed. See other errors for details."

Cause:

The most prominent cause of this problem is that the P_ID page was marked as allocated in a PFS page. But, when the page was read, the reading failed resulting in this error.

Resolution:

To resolve this problem, you would need to use the following methods ideally in the given order:

Resolve hardware-related problems: You should try out the following measures to fix the hardware issues that may have caused this problem:

Check the Windows Application logs and MS SQL Server Error logs to see if the error has really caused because of hardware corruption.

Fix the errors that occur after running hardware diagnostics.

Try to swap the hardware components to see if the error is reproduced or not.

Reinstall the operating system after formatting the hard drives.

Restore from backup: If you are unable to find any hardware-related issue, then you should check the status of the database backup. If it is clean and updated, then you should restore the database from the backup.

Execute DBCC CHECKDB: Lastly, you can run the DBCC CHECKDB tool with the suggested repair clause to repair the damaged database.

However, if you still are getting the similar errors then you should repair the damaged database using a third-party master database file recovery software. These SQL recovery tools are extremely non-destructive in nature that do not damage the corrupt database any further.

The MS SQL Server recovery software that is recommended by most database recovery experts is Stellar Phoenix SQL Data Recovery. With the capability to recover various database components including tables, NDF files, collations, stored procedures, triggers, defaults, etc, this.MDF recovery software is supported by MS SQL Server 2008, 2005, 2000, and 7.0. Also, this MDF file recovery tool is compatible with Windows 7, Server 2008, Vista, Server 2003, XP, and 2000.

Mark Willium is a technical writer working on the Stellar SQL database recovery software.

How to repair SQL database when Error 8903 occurs in MS SQL Server 2000 database

markwillium — Fri, 15 Oct 2010 04:26:19 -0800

In the MS SQL Server databases, the IAM (Index Allocation Map), GAM (Global Allocation Map), SGAM (Shared GAM) are different types of pages that are used to store the records on the hard disks. These pages combine together in an extent, which is used to hold the metadata of the databases. A lot of times due to the mismatching in these files, the database gets corrupt and does not work properly. In such cases, you should try to repair MDF file using appropriate measures. However, if the problem is not addressed, then there is a strong case of using a third-party SQL repair software.

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

“Extent E_ID in database ID DB_ID is allocated in both GAM GAM_P_ID and SGAM SGAM_P_ID.”

Cause:

The error has occurred because of corruption in the extents due to the irregularities in the IAM, GAM, and SGAM pages.

Resolution:

To overcome such corruption issues, you should perform the following methods ideally in the given order:

Fix the hardware corruption issues: As is seen in such cases, the main reason for corruption is the malfunctioning of the hardware parts due to various reasons. You should try to minimize its repercussions using the following measures:

Check the Windows application logs and the SQL Server error logs to see whether the error is a consequence of hardware failure.

Run the hardware diagnostics and fix the error(s), if any.

You should swap the hardware components to isolate the exact error of corruption and try to repair the issue.

If the problem is persisting for a long time, then check if write-caching is enabled on the disks. If yes, then contact your hardware vendor to replace the disk.

In the end, you can try to convert to a new system be reinstalling the operating system after formatting the hard disks.

Restore from database: If the hardware parts are perfectly in place, then you should restore database from the backup, if it is clean and updated.

Execute DBCC CHECKDB: If nothing works out, then you should run DBCC CHECKDB with the repair clause to repair MDF file.

If the issue is still not resolved, then you should use a third-party SQL repair software to repair corrupt SQL database. With the help of these MDF file repair tools, you can get all the data without inflicting any damages.

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

Source: http://hubpages.com/hub/How-to-repair-SQL-database-when-Error-8903-occurs-in-MS-SQL-Server-2000-database

How to Protect Your Microsoft SQL Server Database

markwillium — Tue, 28 Sep 2010 02:56:37 -0800

When the server or database system of MS SQL Server 2008 or 2005 crash, it’s very difficult to recover the original data backup with MS SQL code, but its not impossible. MS SQL Server database unlike other databases such as FoxPro can copy data files; the former must have a backup strategy in order to secure data backup recovery. So take an appropriate backup & recovery operation to recover corrupted data, the data of MS SQL Server 2008 and 2005 can be safely protected.

Restore vs. Recovery

Restore and recovery are two different concepts, but in the database recovery process is also closely linked together. The difference between restore and recovery is given below:

Restore is equivalent to rebuild the part or whole of the database from a backup. It can not change the state of database, such as offline and online.

Recovery of database means it restore the database from offline to online state for users to use.

In Microsoft SQL Server database “Recovery” the database will no longer be able to operate the “Restore”.

A good backup and recovery plan for Microsoft SQL Server should cover the following steps:

1. Need data protection.
2. Daily / weekly / monthly backup plan.
3. Documented verify and the results of the test.
4. Documented the recovery process.

From Microsoft SQL Server 2005, MS SQL Server provides a lot of smart backup methods to recover damaged SQL server database. The main purpose of backup SQL Server database is to reduce the data loss, which asking for zero data loss, and need shorter interval of time to backup the data.

If you are facing data loss problem of SQL server database due to any reasons and not maintain your backup then you have to need smart third party SQL server recovery software to recover SQL database.

Stellar Phoenix Database Recovery software for SQL database is the best option to recover corrupted SQL database. It repairs and restores the database after almost all corruptions issues. It supports recovery of databases created in Microsoft SQL 7.0, 2000, 2005 and 2008. It repairs and restores MDF as well as NDF files of SQL server database.

Source: http://hubpages.com/hub/How-to-Protect-Your-Microsoft-SQL-Server-Database