Resolving Error 8998 In Corrupted SQL Server 2000 Database Article

	1888 Articles Home \| Computer Articles \| Data Recovery Articles \| Windows Articles	Data Recovery RSS
Resolving Error 8998 in corrupted SQL Server 2000 database

The paging feature in SQL Server databases is used to logically split large portions of data into manageable pages. These pages are contiguously associated with each other and can be addressed from one another. However, sometimes because of corruption in the databases the pages do not work in a desired manner.

Author: Mark Willium

Article Tools:

Such situations can occur due to various reasons such as virus infections, power outages, damaged hardware corruption, etc. You should try to repair SQL database using in-built methods. If you are not able to do this, then you should use a third-party SQL repair software to do this.

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

"Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify database ID DB_ID pages from P_ID1 to P_ID2. See other errors for cause."

Cause:

The root cause of this error is that either or all of GAM, SGAM, or PFS pages are corrupted. Because of this, the mapping range of these pages cannot be checked by the CHECKDB command. Here, P_ID1 and P_ID2 represent the ranges of the damaged area.

Resolution:

To resolve this erroneous situation, you should repair SQL database. For this, you should perform the following methods, preferably in the given order:

Check for hardware issues: First of all, you should verify if the error has arose because of malfunction in any hardware component by checking the error logs. You should also try to swap the hardware components to zero-in on the actual error. You should also consider reformatting the hard disks and reinstalling the operating system.

Restore database from backup: If the issue is not hardware related, then you should check if the backup is updated and clean. If yes, then restore the database with its backup.

Run DBCC CHECKDB: If the backup is not updated, then you should run the DBCC CHECKDB command without any repair clause to know the level of corruption. Then, run it again with the suggested repair clause. This tool would be able to resolve the issue.

However, if the problem is persisting then you should use a third-party SQL server recovery software to recover the corrupted database. Such tools are read-only in nature that do not overwrite the existing database.

Stellar Phoenix SQL Database Recovery is an SQL repair software that is able to repair SQL databases from all instances of corruption. It is designed to restore databases created in SQL Server 2000, 2005, and 2008. This MDF repair tool is repairs various database components such as tables, queries, stored procedures, defaults, triggers, etc. It is compatible with Windows 7, Vista, Server 2003, XP, and 2000.

About 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. During research found many repair & recovery software for SQL database, some of them are sql server recovery, sql database recovery, sql repair, recover sql, mdf database repair and many more. For More Details Visit: http://www.mdfrecovery.com/

Article Source: http://www.1888articles.com/author-mark-willium-32501.html

Resolving Error 8998 in corrupted SQL Server 2000 database