Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
jelifah
Starting Member
1 Post |
 Posted - 2011-10-05 : 12:51:49
|
| Any thoughts on how to clear up a db in SQL 2005 SP 3 marked as (Suspect)?Lengthy Background:Running SQL Server 2005 SP3 to host databases for MOSS 2007. On 10/4, around 11:00AM, I started a full index crawl of a 37GB content database. Within 30 minutes the server became bogged down and slow. So slow that when attempting to login locally, press ctrl-alt-del, the screen would just go completely clear and not present anything.Hoping the data crawl was just hogging resources I waited until this morning at 6AM. Issue still existed. I forced the power off of the server, and upon reboot everything came up and seemed fine. 2 hours later the server became inaccessible again. I assume this was because the crawl started up again? But that's just a guess. So I just immediately forced a reboot.This time, on power up, SQL marked SharedServices_1 db as suspect. Now the MOSS sites continue to be reachable 4 hours later, I assume because the crawl can't start with the db offline.Any thoughts to resolve the (suspect) db would be appreciated.Thanks |
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2011-10-05 : 13:17:01
|
| Restore from backup.This is a sharepoint database and repair is not supported and (because of the way sharepoint works with the database) could leave you with a useless sharepoint site.You also need to do some diagnostics on your IO subsystem. It's either faulty or mis-configured as as reboot (even a forced one) should not leave a database suspect.--Gail ShawSQL Server MVP |
 |
|
|
jackv
Master Smack Fu Yak Hacker
2179 Posts |
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2011-10-07 : 03:02:50
|
quote:
Originally posted by jackv
Check some notes on Suspect database : http://www.sqlserver-dba.com/2011/10/sql-server-database-suspect-state.html
Some comments on that:A missing or inaccessible file does not leave a database suspect. The resultant state is RECOVERY_PENDINGKilling a DBCC command can't leave the DB suspect.Killing a large transaction can't leave the database suspect unless there's also some corruption involved.The suspect state requires that SQL started a rollback or crash recovery and that process failed part-way through.--Gail ShawSQL Server MVP |
|
|
|
rozenritz
Starting Member
1 Post |
Posted - 2012-01-03 : 03:18:33
|
| If you find your SQL server 2005 marked as suspect then it suggested to format the entire database. Make sure you create complete backup before the formatting process. In case if you encounter a data loss situation then instead of panicking make use of a genuine MS SQL database repair software tool to repair sql database and recover lost data from it.[url=http://www.mssqldatabaserepair.org][/url]http://www.mssqldatabaserepair.org |
|
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2012-01-03 : 05:08:02
|
quote:
Originally posted by rozenritz
If you find your SQL server 2005 marked as suspect then it suggested to format the entire database.
Really???? And pray tell, how does one 'format' a database? Or was that just an attempt to sound useful in order to plug some software?--Gail ShawSQL Server MVP |
|
|
|
|
|
|
SQL Database marked (suspect)