SharePoint Content Database in Suspect Mode

If you are getting this error message while accessing SharePoint

"Cannot connect to the configuration database" 

There can be several reasons for this and some of them are described here with possible solutions
http://support.microsoft.com/kb/823287

but another reason is that when your database goes to suspect mode you will get the same error.

What Does Suspect Mode Means?

There are different reasons for database to go in suspect mode like error in its physical files e.g:- log file.

It is difficult to make database online when made as suspect database. There are several ways we can identify that a database is in suspect mode.


I used the following commands to bring my database online



exec sp_resetstatus DBNAME

ALTER DATABASE DBNAME SET EMERGENCY
GO

ALTER DATABASE DBNAME SET SINGLE_USER
GO


DBCC CheckDB (DBNAME , REPAIR_ALLOW_DATA_LOSS)
GO

ALTER DAtabase DBNAME SET MULTI_USER
GO



examples of these command with DBNAme is


exec sp_resetstatus 'SharePoint_Config_703e926e-d84f-4ab1-941e-308e85137400'
ALTER DATABASE [SharePoint_Config_703e926e-d84f-4ab1-941e-308e85137400] SET EMERGENCY
GO
ALTER DATABASE [SharePoint_Config_703e926e-d84f-4ab1-941e-308e85137400] SET SINGLE_USER
GO
DBCC CheckDB ([SharePoint_Config_703e926e-d84f-4ab1-941e-308e85137400] , REPAIR_ALLOW_DATA_LOSS)
GO

ALTER DAtabase [SharePoint_Config_703e926e-d84f-4ab1-941e-308e85137400] SET MULTI_USER
GO