web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

The Next Big Bite | Aussie Classics & Starting Small with Clay Wesener | EP04
Check out the Community Spotlight Video Series
News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / SQL Data base - Suspect
Microsoft Dynamics AX (Archived)

SQL Data base - Suspect

(0) ShareShare
ReportReport
Posted on by Community Member

Suddenly we have noticed out live POs data base is in suspect status. Have tried different steps to recover but we are unable to. Getting error as "database cannot be opened. it has been marked suspect by recovery. see the sql server errorlog for more information.". Could any one please help.

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    vijaysharma Profile Picture
    vijaysharma 2 on at

    HI,

    Trouble Shooting Steps:

    1. Change the status of your database.

    2. Set the database in 'Emergency' mode such as:  Query: ALTER DATABASE <DatabaseName> SET EMERGENCY

    3. Check for any of the inconsistency by using Query: DBCC checkdb('DatabaseName')

    4. Bring the database to MULTI USER mode  Query:-ALTER DATABASE [DatabseName] SET MULTI_USER

    5. If any error message even after using DBCC CHECKDB command, then quickly bring the database in SINGLE USER MODE by running the query mentioned below:

    Query :-ALTER DATABASE <DatabaseName> SET SINGLE_USER WITH ROLLBACK IMMEDIATE;

     

  • Suggested answer
    guk1964 Profile Picture
    guk1964 10,888 on at

    What version/cu of SQL?

    There can be many reasons for a SQL Server database to go in a suspect mode when you connect to it - such as the device going offline, unavailability of database files, improper shutdown etc.

    You may very well be at the point where data loss is at risk. So stop using the system.

    Before shutting it down, export all windows logs so that you can read those from another system. I e Application, security ....

    Take all logs from the directory containing the errorlog

    Safety first :

    Salvage what can be salvaged - just in case.

    Copy all LDF, MDF and NDF files from this subsystem disk to another disk.

    Set up another SQL on a healthy system (i e OS and disk subsystem  to use to investigate the damaged database.

    Investigate  to see what can be done. e.g. use the previous suggest steps basically :

    1.Reset the suspect flag

    2.Set the database to emergency mode so that it becomes read only and not accessible to others

    3.Check the integrity among all the objects

    4.Set the database to single user mode

    5.Repair the errors

    6.Set the database to multi user mode, so that it can now be accessed by others

    If no joy, then I recommend get professional help fast.

    Also check when was your last good back up and see whether you can recover that e.g. to a a test system.

    Good luck.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

The Next Big Bite | Aussie Classics & Starting Small with Clay Wesener | EP04
Check out the Community Spotlight Video Series

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the June Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans