My SQL Server 2008 R2 database was stuck in suspect mode. The database was no longer accessible. I tried restoring it by setting it to ‘EMERGENCY’ mode and then executed the DBCC CHECKDB command with REPAIR_ALLOW_DATA_LOSS option. Executing the query returned SQL error 8921. The complete error message reads:
Msg 8921, level 16, state 1, line 1
“CHECKTABLE terminated. A failure was detected while collecting facts. Possibly temp DB out of space or a system table is inconsistent. Check previous Errors.”
After some research, I found that the error occurs when the tempdb database runs out of space or the system tables are corrupted. The only solution I could find was to restore the database from backup. But, I didn’t have an updated backup available.
I decided to use a professional SQL database repair tool to fix database corruption. That’s when I came across Stellar Repair for MS SQL software.
What made me choose Stellar Repair for MS SQL?
The software offers remarkable features making it the most preferred SQL database repair software among users. Some of them are listed as below:
- Repairs database files (MDF or NDF) on Windows and Linux-based systems
- Recovers complete database objects from the corrupted file, including tables, keys, indexes, triggers, stored procedures, etc.
- Multiple file saving formats to save repaired file, including CSV, HTML, and XLS
- Allows selecting specific database components that you wish to restore
- Can restore database stuck in ‘suspect mode’, ‘recovery pending state’, and ‘restoring state’, etc.
How Stellar Repair for MS SQL Works?
Before you proceed with repairing a corrupt SQL database with Stellar Repair for MS SQL software, your PC must meet the following system requirements:
- MS SQL Server: MS SQL Server 2019, MS SQL Server 2017, MS SQL Server 2016, MS SQL Server 2014, MS SQL Server 2012, MS SQL Server 2008 R2, 2008, 2008 (64 bit), 2008 Express, MS SQL Server 2005, 2005 (64 bit), 2005 Express, MS SQL Server 2000, 2000 (64 bit), 7.0 and mixed formats.
- OS: Windows Server 2012/2008/2003 and Windows 10/8.1/8 /7
- Processor: Intel-compatible (x86, x64)
- Memory: 8 GB (recommended) 4 GB (minimum)
- Hard Disk: 250 MB for installation files
Step 1: Launch the software. This opens a ‘Select Database’ window with options to ‘Browse’ or ‘Search’ the corrupt database.
Note: Use the ‘Search’ to find the databases whose location is unknown.
Step 2: Once the SQL database file is selected, click ‘Repair’ to begin repairing the file.
Step 3: The software displayed two scan mode options: Standard Scan and Advanced Scan. It is recommended that you run the ‘Standard Scan’ for repairing the SQL database file quickly. While the ‘Advanced Scan’ option is for the users who can invest time in thoroughly scanning the corrupted SQL db file. After selecting the scan mode, click OK.
Note: The repair process can take hours to days, depending on your database file’s size.
Step 4: Once the software completes repairing the .MDF file, a ‘Repair Complete’ message box appears.
Step 5: Clicking OK opens a preview window displaying all the repairable database objects. The objects are listed on the left-pane, while the contents of an individual object is displayed on the right-pane.
Step 6: For saving the repairable SQL objects, click Save on the File menu.
Step 7: Select MDF file format for saving the repaired SQL database file, choose the location (default or new) for saving the file, and then enter details to connect to SQL Server. Click OK.
Step 8: When prompted with ‘Save Complete’ message box, click OK.
Executing these steps will repair your SQL database at the specified location.
Despite taking precautionary measures to keep the SQL databases from turning corrupt, the database can still become corrupt at any time. Troubleshooting the corrupt SQL database manually can lead to increased database downtime and business loss if not handled properly. Stellar Repair for MS SQL is an effective and must-have tool that can easily repair a corrupt MDF file in a few simple steps. All you need to do is select the corrupted file, scan and repair it for errors, and then save the repaired file.