Sql server database suspect mode error???

Question

What could be the reason for going into the server's suspense mode?????

Gajendra Jangid · Answer

https://www.stellarinfo.com/blog/recover-sql-database-from-suspect-mode/

Dharmraj Thakur · Answer

Just replace your database name with this query... Alter Database [dbname] set Emergency Alter Database [dbname] set Single_User dbcc checkdb ('dbname'repair) with no_infomsgsall_errormsgs Alter Database [dbname] set Multi_User

Sanwar Ranwa · Answer

suspect mode error means the server suspects the primary filegroup of the database to be damaged. When SQL database goes into suspect mode it becomes inaccessible. Under such a situation neither will you be able to connect to the database nor will you be able to recover it during the server startup. You’ll need to perform some alternative recovery actions to resolve the issue

Rupesh Kahane · Answer

May be 1) A query gets suspended when it is requesting access to a resource that is currently not available. This can be a logical resource like a locked row or a physical resource like a memory data page. The query starts running again once the resource becomes available. 2) High disk IO means that a lot of data pages need to be accessed to fulfill the request. That is all that I can tell from the above screenshot. However if I were to speculate you probably have an IO subsystem that is too slow to keep up with the demand. This could be caused by missing indexes or an actually too slow disk. Keep in mind that 15000 reads for a single OLTP query is slightly high but not uncommon. 3) The session is waiting for an event such as I/O to complete. http://msdn.microsoft.com/en-us/library/ms174313.aspx