The database is marked as suspect because it failed the recovery process that brings a database to a consistent transactional state. This can occur during the following operations:
Starting up an instance of Microsoft® SQL Server™ 2000 or SQL Server 2005.
Attaching a database.
Using the RESTORE database or RESTORE LOG procedures.
Inspect the Microsoft SQL Server error log and determine the cause of the error. If SQL Server has been restarted since the failed recovery, look at previous SQL Server error logs to see the reason why recovery failed.
If the recovery failed because of a persistent I/O error, a torn page, or other possible hardware problem, resolve the underlying hardware problem and restore the database by using a backup. If no backups are available, consider the repair options of DBCC CHECKDB.
If you are unable to resolve this problem, contact your primary support provider. Have the SQL Server error log available for review.