Home » Topic » How to repair Suspect database in SQL Server?

How to repair Suspect database in SQL Server?

Michael Scofield ~ Modified: October 27th, 2017 ~ ~ 1 Minute Reading

Home › Forums › How to repair Suspect database in SQL Server?

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • October 27, 2017 at 7:14 am #5396 Score: 0
    Michael Scofield
    Moderator
    20 pts

    I am facing a very problematic situation while using my SQL Server database 2014 as I am unable to connect with one of my SQL databases and it has been marked as Suspect. Due to this, I haven’t been able to access my work-related data at all. Can anyone help me to get rid of this problem?

    October 27, 2017 at 8:24 am #5403 Score: 0
    Kerry Morris
    Moderator
    34 pts

    Hey Michael,
    I see that you are facing the error of Suspect Database. Let me first ask you a simple question to pinpoint the source of the problem. Did something unusual happen since the time you last connected to this specific database?

    October 27, 2017 at 8:51 am #5404 Score: 0
    Michael Scofield
    Moderator
    20 pts

    Yes, as a matter of fact, there was a sudden power failure which caused my system to shut down improperly. Since then, I am facing this difficulty of not being able to connect to my database.

    October 27, 2017 at 9:09 am #5405 Score: 0
    Kerry Morris
    Moderator
    34 pts

    Thanks for the information. I think the main reason for your SQL Server database to have entered into suspect mode is that the internal MDF files have become corrupted due to the power failure event.
    You can use some commands such as DBCC CHECKDB to check errors and then use a series of commands to repair suspect database. Let me know if you are successful using this method.

    October 27, 2017 at 9:44 am #5407 Score: 0
    Michael Scofield
    Moderator
    20 pts

    I tried performing the commands you mentioned but the manual approach did not prove helpful to me as it was very difficult to implement it properly. Also, I found that the act of committing mistakes could not be avoided while following the manual method. Is there any other simpler and faster alternative that you can share with me?

    October 27, 2017 at 10:50 am #5410 Score: 0
    Kerry Morris
    Moderator
    34 pts

    In that case, I would recommend you to make use of the services of an automated tool which is mentioned in the following blog post.

    Check it out here : http://lettoknow.com/recover-sql-database-from-suspect-mode-or-recovery-pending/

  • Author
    Posts
Viewing 6 posts - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.