I have two questions:
(1) How can we diagnose the reason of database suspect? The error log
doesn't tell me much.
(2) After restart the server, the suspect is gone, but how can I
ensure everthing is fine? DBCC check?
Thanks!
Saiyou

1. Most common causes for suspect status are missing devices, invalid
datafiles/drives, insufficient disk space, interruption during restore etc.
Sorry, I do not have a to-the-point answer, if you cannot find any
information in the error log.
2. http://support.microsoft.com/default...b;en-us;255599

--
- Anith
( Please reply to newsgroups only )

To add to Anith's response, there should be some indication in the error
log. If there is no self-explanatory message text but a Win32 error
code is listed, you can get the message text from the command prompt
using NET HELPMSG. For example:

NET HELPMSG 32

Yeilds:

The process cannot access the file because it is being used by
another process.

A common cause this transient suspect database problems is anti-virus or
backup software that is using a database file when SQL Server tries to
open it.

--
Hope this helps.

Dan Guzman
SQL Server MVP

-----------------------
SQL FAQ links (courtesy Neil Pike):

http://www.ntfaq.com/Articles/Index....partmentID=800
http://www.sqlserverfaq.com
http://www.mssqlserver.com/faq
-----------------------

"Saiyou Anh" <wangc@alexian.net> wrote in message
news:a51d3ca7.0308070732.9c3c574@posting.google.co m...
> I have two questions:
> (1) How can we diagnose the reason of database suspect? The error log
> doesn't tell me much.
> (2) After restart the server, the suspect is gone, but how can I
> ensure everthing is fine? DBCC check?
> Thanks!
> Saiyou