Image IT (3/20/2011)
Which I/O subsystems you mean?
The one that the suspect database is stored on.
Can it be because of the replication configuration?
Suspect means SQL encountered data or log file damage during crash recovery or during a rollback
Because its a replicated sever, what u think will be easiest:
1. to try and recover the suspect DB
2. to reinitialize the replication all over again (off course after try and find out the reason of the "suspect" situation)?
Without seeing the messages in the error log that explained why SQL marked the DB as suspect I would rather not theorise on an optimal recovery.
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)SQL In The Wild
: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter
We stand on the bridge and no one may pass