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
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
