Hello!

Recently I did the unthinkable.  I became impatient while some Windows updates were being applied to a SQL Server.  I thought they actually were stuck because it was stuck on one update for several minutes.  I therefore tried to stop the updates.  Well instead of stopping the server became unresponsive.  And instead of waiting a while I decided to perform a hard-boot.  Not good.  This left many of my databases in suspect mode and all my applications using that server were dead.    Fortunately I was able to recover them and get things working again.  Primarily because I found a great fix on managed.com.  see below for sql and URL:

EXEC sp_resetstatus [YourDatabase];

ALTER DATABASE [YourDatabase] SET EMERGENCY

DBCC checkdb([YourDatabase])

ALTER DATABASE [YourDatabase] SET SINGLE_USER WITH ROLLBACK IMMEDIATE

DBCC CheckDB ([YourDatabase], REPAIR_ALLOW_DATA_LOSS)

ALTER DATABASE [YourDatabase] SET MULTI_USER

https://support.managed.com/kb/a398/how-to-repair-a-suspect-database-in-mssql.aspx