A database in suspect state restricts access to data or settings. Data in suspect databases can not be pulled out nor you can perform recovery operations. In such cases, no matter the problem is due to any corrupt data page or log file, recovery is a night mare. SQL Server 2005 has introduced a very useful state for working with suspect databases. You can set the suspect database to emergency state and then exploit the wide range of operations on data and settings.
dbDigger, Disaster Recovery, Enhancement in new versions, Publications of Atif Shehzad on MSSQLTips.com
Click here to read full article with practical examples about using the Emergency State for a Corrupt SQL Server Database.