How to overcome Error 8921 in MS SQL Server 2000 database

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

»»  Read More...

DBCC DBREINDEX Fails to Rebuild Microsoft SQL Server Database Indexes

Microsoft SQL uses indexes to effectively manage the database and improve its performance. It helps database manager to easily locate the specified table and extract it. However, in some situations the indexes may get damaged due to high fragmentation and database may become inaccessible. To overcome such issues, SQL provides you a tool, called DBCC DBREINDEX, to rebuild the database indexes. But, sometimes, this tool fails to work and database remains in unusable state. This behavior leads to critical data loss situations and requires SQL database recovery to be fixed, if there is no updated backup in place.

In a practical situation, access violation may occur in CTableMetadata::LoadIndex function when you run the DBCC DBREINDEX on an SQL Server table that contains hypothetical indexes. Such indexes are created by Index Tuning Wizard during tuning process. They are generally dropped at the end of Index Tuning Wizard procedure. But, sometimes these indexes are not deleted correctly.

Furthermore, you may come across the below error message when you run the DBCC CHECKDB utility on problem database:

"Server: Msg 7995, Level 16, State 3, Line 1
Database 'test' consistency errors in sysobjects, sysindexes, syscolumns, or systypes prevent further CHECK processing."

The above error indicates that sysindexes table is corrupt. If you run the DBCC CHECKTABLE on corrupt sysindexes table, further errors occurs that resembles the followings:

Server: Msg 2537, Level 16, State 40, Line 1
Table error: Object ID 2, index ID 0, page (1:3282), row 5. Record check (length Resolution:

In order to sort out this behavior, you need to restore affected SQL database from the most recent backup. A valid and updated backup is the most effective way to perform SQL Server recovery.

In case the backup is not available or updated, you are required to opt for MS SQL recovery software to ensure absolute and safe recovery.

MDF recovery applications use highly-advanced scanning methods to successfully recover corrupt SQL Server database in all corruption scenarios. They have simple graphical user interface and read-only conduct to offer easy and safe recovery.

Stellar Phoenix SQL Recovery is the most advanced and efficient utility to successfully recover inaccessible data from corrupt SQL database. The software repairs both MDF and NDF files of Microsoft SQL Server 2008, 2005, 2000, and 7.0 databases.

»»  Read More...