This is an advanced repair. If at any time you need assistance, you can contact our Technical Support by clicking on the "Live Chat" option on this page.
Generally when the database is marked as suspect it is due to the computer or server shutting down incorrectly and the log being corrupted. You can run four queries to fix this most of the time.
Before running any repair first make sure to backup your database
When you see [database name] replace that with your database name and leave out the brackets. The default names for the database are:
- Genesis: gendata
- Food Processor: eshadata
First change the database to emergency mode:
ALTER DATABASE [database name] SET EMERGENCY
(Enter your database name in and take out the brackets)
Then we will want to change the database to Single User Mode to repair it:
ALTER DATABASE [database name] SET SINGLE_USER
Then we will want to check the database for errors and rebuild the log file:
DBCC CHECKDB('[database name]', REPAIR_ALLOW_DATA_LOSS)
If you don't receive any errors, change the database to multi_user mode:
ALTER DATABASE [database name] SET MULTI_USER
The database should now be fixed and the application should work again.