A database which gets marked as suspect may be caused by starting Microsoft SQL Server when the volume(s) on which it resides is unavailable to this system. When SIOS Protection Suite is used to protect SQL databases, the starting and stopping of SQL should be performed only as a function of bringing hierarchies in or out of service. In those situations where a database has been marked suspect and it is known that the database is fine, perform the following steps to correct the problem.

For those databases which are suspect on a primary/secondary server:

  1. Make sure that the volume(s) where the database resides is actively (green) being protected by this server.
  1. Use sp_resetstatus to change the state of the database. Execute the following commands from a query window to reset the status of the suspect database:

While in master database, execute sp_configure ‘allow updates’, 1

Reconfigure with override

Sp_resetstatus ‘dbname’

Sp_configure ‘allow updates’, 0

Reconfigure with override

  1. Stop Microsoft SQL Server.
  1. Start Microsoft SQL Server.


Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment