Stellar Repair for MS SQL is a data recovery tool for corrupted SQL database objects, such as tables, keys, indexes, views, triggers, stored procedures, rules, and user-defined functions. It can be used to recover databases that have been damaged by a server crash, unplanned database termination, or lack of server disk space.
The software supports various versions such as MS SQL Server 2019, 2017, 2016, 2014, 2012, 2008 R2, 2008, and earlier ones.
There may be various situations for manual methods of repairing MSSQL. There are some options that you can use to perform database consistency checks a DBCC CHECKDB . These options are:
- database_name | database_id | 0: Specifies the name or ID of the database on which you should run integrity checks. If the “database_name” or “database_id” is not specified and “0” is specified, the current database will be used by default.
- NOINDEX: This argument only performs logical checks to reduce the total execution time. Additionally, it does not include non-clustered indexes in checks.
- REPAIR_ALLOW_DATA_LOSS | REPAIR_FAST | REPAIR_REBUILD: To repair a database, you must run the DBCC CHECKDB command with one of these repair options:
- REPAIR_ALLOW_DATA_LOSS: Use this repair option as a last resort to repair a SQL database, as it may result in data loss.
- REPAIR_FAST: This repair option does not perform any repair actions. This helps preserve the syntax for backwards compatibility.
- REPAIR_REBUILD: The REPAIR_REBUILD option allows you to repair the database without any data loss. It can be used to repair missing rows in nonclustered index files and to rebuild an index.
- ALL_ERRORMSGS: This argument displays all error messages for each object.
- EXTENDED_LOGICAL_CHECKS: Starting with SQL Server 2016, additional logic checks are not performed on filtered indexes and views.
- NO_INFOMSGS: DBCC output displays informational messages that are not related to consistency errors. Running DBCC CHECKDB with NO_INFOMSGS can disable informational messages.
- TABLOCK: Uses locks rather than an internal database snapshot to perform consistency checks on a database.
- ESTIMATEONLY: Specifies the estimated space required by the ‘ tempdb ‘ database to execute the CHECKDB command.
- PHYSICAL_ONLY: This limits consistency checks on the physical structure of the database page, reducing DBCC CHECKDB execution time on large databases.
- DATA_PURITY: This allows checking a database for invalid columns or out-of-range values.
- Two-step recovery process: scanning and recovery into a database preview.
- Export feature to save recovered databases in MDF, CSV, XLS, and HTML formats.
- Advanced scan mode for better results on large databases.
- Ability to save recovered databases directly to a live database.
- It is very convenient and a good alternative to manual and server-based recovery procedures.
- Can save time and effort, especially for large databases
- It’s very easy to use and even can be used for non-technical users as well.
Overall, Stellar Repair for MS SQL is a powerful and reliable SQL recovery tool for corrupted SQL databases.
Free version: Installation, scan, and preview
Installation of Stellar Repair for MS SQL is ready and you can take a backup of the MSSQL database. You will have to stop your MS SQL server and copy the database to a different location accessible by the software. After successfully fixing the MSSQL database, you then can move the restored copy of your database back to your SQL server.
Stellar Repair for MS SQL uses a two-way approach which is complete with scanning and recovering the database preview and then the file can be exported which will be a paid version. For scanning, you can simply use MDF or NDF file format and hit the repair button.
If there are multiple database files, you might use the search feature to auto-scan a specific directory for supported database file types.
All supported database files will be shown in a table, which helps if you are unsure about which version you want to restore. Once selected, you can start the repair procedure by hitting the button on the lower right.
Before scanning begins, you can choose any option as a standard or the advanced scan method, which takes substantially more time but gives better results in the advanced version. For huge databases, you might want to try your luck with standard mode. If there is no timing issue, you can try using the advanced mode, which will be a better choice.
After the scan is done, you can browse and search the existing tables. If the complete database you found is recovered then you can save the repaired database you will have to purchase the paid version.
Saving a restored database
Stellar Repair for MS SQL allows you to save the repaired SQL database file into four different formats; MDF, CSV, XLS, and HTML. For MDF you can choose between saving into a new database file and uploading the recovered file into a live database directly after providing the required server credentials.
If you have a corrupted SQL database, Stellar Repair for MS SQL is a good option to consider. It is easy to use and has a good track record of success. However, it is important to note that no data recovery tool is perfect, and there is no guarantee that Stellar Repair for MS SQL will be able to recover your database.