{"id":153,"date":"2010-02-11T12:40:00","date_gmt":"2010-02-11T07:10:00","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=153"},"modified":"2026-09-22T11:26:09","modified_gmt":"2026-09-22T05:56:09","slug":"experience-with-recovering-a-crm-database-marked-as-suspect","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2010\/02\/experience-with-recovering-a-crm-database-marked-as-suspect\/","title":{"rendered":"Experience with recovering a CRM database marked as SUSPECT"},"content":{"rendered":"
\n

Unfortunately we had our CRM down because the CRM database was marked suspect in SQL. Had a tough time getting it back. Here we share our experience and the steps\/commands that helped us get our system back up and running. These may not be the only way of fixing it and perhaps not everyone\u2019s problem would be solved by following these but I hope some of the points below would perhaps get you closer to retrieving your data back.<\/p>\n

– Stop the SQL server service.
\n– Go to Physical location of the suspected database and rename the database.
\n– Create new database of the same name to suspected database name.
\n– Remove the newly created database after this rename suspected database to original suspected database name
\n– Start the SQL server service.
\n– Open SQL server Management Studio and find \u201cnew Query\u201d
\n– Click on new query , new command window will be open.(See below the screen)<\/p>\n

\"\"
\n– Select the master database.
\n– After that in command window type below the statements
\no ALTER DATABASE SET EMERGENCY
\no ALTER DATABASE SET SINGLE_USER
\no DBCC CheckDB (”, REPAIR_ALLOW_DATA_LOSS) WITH NO_INFOMSGS
\no ALTER DATABASE SET MULTI_USER<\/p>\n

Once these commands are successfully processed the database would be available. Note that the DBCC statement above may result in some data loss if any part of the data is corrupt. But if you do not have a SQL backup for you to restore then this is the only option you have\u2026<\/p>\n

——————————————————-
\nPosted by: Inogic
\nFor more information\/discussions (documents, sample code snippets, detailed work flow or diagrams),
\nPlease be free to visit the following links or email us:
\nWeb: http:\/\/www.inogic.com
\nBlog: http:\/\/inogic.blogspot.com
\nEmail: news@inogic.com
\n—————————————————–<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

Unfortunately we had our CRM down because the CRM database was marked suspect in SQL. Had a tough time getting it back. Here we share our experience and the steps\/commands that helped us get our system back up and running. These may not be the only way of fixing it and perhaps not everyone\u2019s problem\u2026 Read More: Experience with recovering a CRM database marked as SUSPECT »<\/a><\/span><\/p>\n","protected":false},"author":13,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[19],"tags":[1652,1685],"class_list":["post-153","post","type-post","status-publish","format-standard","hentry","category-dynamics-crm","tag-sql-error","tag-suspect-database"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t