Discussions
Categories
- All Categories
- 36 Oracle Food and Beverage Virtual Connect
- 3 Other Food & Beverage Discussions
- 3 Oracle MICROS Reporting & Analytics
- 8 Oracle MICROS RES 3700
- 21 Oracle MICROS Simphony
- 1 Oracle MICROS Simphony Essentials
- 8 Stay Current
- 1 Best Practices
- 3 Latest Enhancements
- 4 Product Release Documentation
- 406 Litening Connect Zone
How can I fix MSSQL Suspect Mode error in Simphony?
VladA-Oracle
Employee
How can I fix MSSQL Suspect Mode error in Simphony?
Best Answer
-
Due to some database errors, MSSQL status was changed into Suspect Mode. Run the following queries, individually, in the present order:
EXEC sp_resetstatus ‘dbName’;
ALTER DATABASE ‘dbName’ SET EMERGENCY;
DBCC checkdb(‘dbName’);
ALTER DATABASE ‘dbName’ SET SINGLE_USER WITH ROLLBACK IMMEDIATE;
DBCC CheckDB (‘dbName’, REPAIR_ALLOW_DATA_LOSS);
ALTER DATABASE ‘dbName’ SET MULTI_USER;
Database should now be back to multi-user mode, and ready for read/write.
This discussion has been closed.