Stellar Repair for MS SQL
Stellar Repair for MS SQL
Stellar Repair for MS SQL / 5. FAQs
1. What does the demo version of the software do?
Demo version of the software shows only repairs and displays the preview of the database. To save repaired database, you need to purchase and activate the software.
2. Why do I require Stellar Repair for MS SQL?
Sometimes due to virus infection, operating system malfunction, file system corruption or other similar reasons, the SQL database gets corrupted and the data in it becomes inaccessible. Stellar Repair for MS SQL helps you rebuild the corrupt database and restore the data back.
The software is risk-free and repair inaccessible database components from the corrupt MDF file in three easy steps: Select, Repair and Save. See Working with the Software, to know about the steps.
To know which components of SQL database you can recover by using Stellar Repair for MS SQL, refer to the Knowledge Base Article: https://www.stellarinfo.com/support/kb/index.php/article/which-components-of-sql-database-can-i-recover
3. What are the common SQL Database Corruption Errors, Causes and Resolutions?
Refer to the Knowledge Base Article: https://www.stellarinfo.com/support/kb/index.php/article/common-sql-database-corruption-errors-causes-solutions
4. How to fix the Activation error of Stellar Repair for MS SQL?
Refer to the Knowledge Base Article: https://www.stellarinfo.com/support/kb/index.php/article/fix-sql-database-repair-activation-error
5. Why is it necessary to perform repair process on the copy of database?
Stellar Repair for MS SQL will not be able to repair if the database is attached to MS SQL Server.
6. Can we repair tables in a MDF file selectively?
Yes, you can recover single or multiple tables. Simply select desired tables in tree view and start repair process.
7. Software is not able to detect the Database version what should I do?
There is an option to choose the database version manually. When software fails to detect the version then select the database version manually. See Select the Scan Mode and Repair MDF Files for more information.
To know more, refer to the Knowledge Base Article: https://www.stellarinfo.com/support/kb/index.php/article/software-unables-to-detect-database-version
8. How can Stellar Repair for MS SQL help me search for the location of MDF file on the computer?
You can search for MDF file on the computer using Find option of the software. For more details, please refer Select MS SQL database (MDF File) topic of the help manual.
9. I want to locate an item in the database (MDF file). Is there any way I can do this using the software?
Yes, after repairing the MDF file, the software gives you option to search items in tree view. Use Search option to locate desired item in a table.
10. How to Recover Deleted Records using Stellar Repair for MS SQL?
Stellar Repair for MS SQL provides you an option to Include Deleted Records in MS SQL database (MDF) repaired file. See Include Deleted Records for more details.
To know more, refer to the Knowledge Base Article: https://www.stellarinfo.com/support/kb/index.php/article/recover-sql-deleted-records
11. How Can I Save The Repaired SQL Database In Three Different Formats?
Stellar Repair for MS SQL software allows you to save the repaired SQL database file in New Database, Live Database or Other formats such as CSV, XLS or HTML format.
To save the repaired SQL database file in any one of the three file formats, Click Save from File ribbon. A Save Database dialog box appears giving you the option to save in New Database, Live Database or Other formats such as CSV, XLS or HTML format. Fill in the details and click Save. See Preview and Save MDF Files for more details.
To know more, refer to the Knowledge Base Article: https://www.stellarinfo.com/support/kb/index.php/article/save-repaired-sql-database-in-four-options
12. Why is it taking longer than usual to save a table?
If it takes longer than usual to save a table, how would I recognize the issue?
At the time of the saving process, if the process stops at a specific percentage and is not increasing, check the saving percentage of that table after some time, if it is still not increasing, then follow the steps to check if the file is stuck or not in the MS SQL Server:
Run MS SQL Server.
In Object Explorer, connect to an instance of the SQL Server Database Engine.
Expand Databases Folder, find the recovered database in Object Explorer, and expand it.
Expand Tables Folder, by searching the name of the tables that are stuck in between the saving process, preview the records by using SQL statement “SELECT * FROM table_name;”. You have to execute this statement twice or thrice to see the records/rows counter.
If the records counter in the right-bottom of the screen is increasing, that means the saving process is working appropriately and you don't have to do anything.
If the records counter in the right-bottom of the screen is not increasing, that means the saving process is stuck.
13. I am trying to save the repaired database but the software is saving particular tables for quite some time. I am not sure if the software is doing anything in the background. How can I save the tables?
If the software is taking time to save the database or the specific percentage and is not increasing, that means the process is stuck.
If the process gets stuck, you have to stop the Saving Process from the Saving Table dialog box. After stopping the process, by default, stuck tables are already selected in the left pane of the screen.
You have to save the stuck tables individually.
To save the tables follow the steps given below:
From File menu, click Save.
Save Database window appears. From Saving Option, select Live Database radio button.
A Connect to Server window appears. Enter Server Name/Instance Name.
From the drop-down list, choose Existing Database (previously recovered database).
Select the Save Mode option: Fast Saving / Standard Saving. Click Save to continue the process.
Save Complete dialog box appears, with a message “File saved successfully”, indicating that the saving process is completed successfully.
To know more about the saving process, refer Preview and Save MDF Files.
14. I am not satisfied with the repaired results. What can I do?
If in case you are not satisfied with the repaired results, we recommend getting your file repaired by certified professionals.
15. How can we view process log?
You can view log of the process at the bottom of the user interface. If this pane is not visible, you can enable it by selecting the Log Window checkbox in View section of View ribbon.
16. Can we save process log?
Yes, Stellar Repair for MS SQL gives you option to save log report of the process.
To save log report:
From View ribbon, select Save Log.
In Save As dialog box, select the location where you want to save the log report. Click Save.
To know more, refer to the Knowledge Base Article: https://www.stellarinfo.com/support/kb/index.php/article/save-log-report-of-complete-repair-process
17. How to Customize Quick Access Toolbar Feature in the Software?
Refer to the Knowledge Base Article: https://www.stellarinfo.com/support/kb/index.php/article/customize-quick-access-toolbar-of-the-software
18. How much time Stellar Repair for MS SQL will take to scan and repair corrupt/damaged database?
The time taken in scanning and repairing database is totally dependent upon the size and number of records present in database file.
19. Is MS SQL application is required to be installed on the system for previewing database?
No, MS SQL application is not required to be installed for previewing the database.
20. How to fix connection error when trying to save the repaired SQL database in New or Live Database?
When you are trying to save repaired MS SQL Database in Live or New Database you might face a “Connection Error”. This can be because the Stellar Repair for MS SQL software and the server where the database is deployed are installed on two different machines. The Stellar Repair for MS SQL must be installed on the same server machine where the database is deployed when you are trying to save the Database by using the New or Live Database option.
21. How to Use Platinum Version of Stellar Repair for MS SQL?
Refer to the Knowledge Base Article: https://www.stellarinfo.com/support/kb/index.php/article/platinum-version-of-stellar-repair-for-ms-sql
21. How to Recover SQL Database from SUSPECT Mode?
Refer to the Knowledge Base Article: https://www.stellarinfo.com/support/kb/index.php/article/procedure-to-recover-sql-database-from-suspect-mode
22. How to create a New SQL Server Database to Save a Repaired Database File after Corruption?
Refer to the Knowledge Base Article: https://www.stellarinfo.com/support/kb/index.php/article/save-repaired-sql-database-file-after-corruption
23. How many tables can be saved at the same time?
Stellar Repair for MS SQL save eight tables at the same time. (The processing of the table depends upon the Processor and RAM of the system)
24. How many scanning modes are there and what is the difference between the both?
There are two scanning modes, Standard Scan and Advanced Scan. Standard Scan is recommended for fast scanning procedure which is successful in most cases of corruption and Advanced Scan extensively scans the corrupted files, it takes more time but works effectively when Standard scan is not working.
25. What is the difference between Fast Saving Mode and Standard Saving Mode?
Fast Saving mode is advisable for large databases. It saves the data first and then save indexes. There is a possibility that the administrator may have to reapply indexes after the repaired database is saved.
Standard Saving Mode is a conventional way of saving repaired databases.It saves the data and the indexes at the same time.
26. Can I repair the database using the existing saved scan information?
Yes, you can repair the database using the existing saved scan information.