To find corruption in SQL server is a frustrating part for organizations. After display of error messages, most organizations run DBCCCHECKDB command for acknowledging whether corruption is logical or physical in SQL database. When this command is used with REPAIR_ALLOW_DATA_LOSS, it helps repairing error messages often occurs but it gives no surety of data safety. Sometimes, when you run DBCC CHECHDB command along with REPAIR_ALLOW_DATA_LOSS, you will find database damage as fixed but actually it is fixed.
How to Overcome such Issues?:
Error Message: Take an instance; you are using SQL 2000 and get an error message 8909
"Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (1:192). The PageId in the page header = (0:0).
Further, you use DBCC CHECKDB with REPAIR_ALLOW_DATA_LOSS option and it reports it as fixed. But again, when you run DBCC CHECKDB command to check database integrity, it reports the same error messages."
In order to know How to Repair MS SQL 2000 database, you can give a try given below methods:
Our SQL Recovery software is a useful solution to easily cope with error messages and repair mssql database. This MSSQL repair tool scans and repair corrupt sql database data easily. This SQL database repair software runs with all Windows OS editions thus used globally.