Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
?
Solved

how do you fix databases that are in suspect mode.

Posted on 2009-04-15
5
Medium Priority
?
562 Views
Last Modified: 2012-05-06
We have a SQL server 2000 database that is in suspect mode. how do I recover from this.

0
Comment
Question by:Steve Samson
5 Comments
 
LVL 8

Accepted Solution

by:
SNilsson earned 2000 total points
ID: 24151620
0
 
LVL 20

Expert Comment

by:Marten Rune
ID: 24151855
Look at the posting:
http://www.experts-exchange.com/Microsoft/Development/MS-SQL-Server/SQL-Server-2005/Q_24180816.html

When did it get suspect, after a restart? Do you have a antivirus program on the server, it might hog the physical files, and hence the server can not access them. Stop and start the SQL Services to find out.

Check the log for errors, is it possible that your harddrive is failing. If so you better find out fast.

Can you provide more info on when it got suspected, if you tried a SQL server restart. Is it the only database on the sql. What SP is your SQL running, on what OS?

/Marten
0
 
LVL 7

Expert Comment

by:Hemantgiri S. Goswami
ID: 24154562
Hi,
I would recommend to follow the instruction given here to recover the suspected database http://www.myitforum.com/articles/18/view.asp?id=7381
0
 
LVL 20

Expert Comment

by:Marten Rune
ID: 24155171
Good article ghemant

For the author ccutler:
two things to emphasize
1. If you need to use the 'repair_allow_data_loss' switch with DBCC. Maybe it's a better approach (assuming the db is in full recovery mode) to  make a tail log backup, and then simply drop and restore the database the normal way. If it's not in full recovery mode but in simple, check your SLA. You'll most likely find that a data loss of transactions up to 24h is acceptable (maybe the application can rerun those by design on appserver or clients). It should be evaluated if it's better to know that all the data is correct, but transactions for this day needs to be done all over.
2. If DBCC finds that your database files has been damaged, check the log for errors regarding to disk failure, typically 823, 824 and 825 (825 is a warning, the other are failures). These indicate that there is something wrong with the I/O subsystem. You need to find out why corruption occurred, it will most likely occur again so preventive actions needs to be taken.

/Marten
0
 

Author Closing Comment

by:Steve Samson
ID: 31570644
Worked like a charm.
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In this article we will learn how to fix  “Cannot install SQL Server 2014 Service Pack 2: Unable to install windows installer msi file” error ?
This month, Experts Exchange sat down with resident SQL expert, Jim Horn, for an in-depth look into the makings of a successful career in SQL.
Via a live example, show how to shrink a transaction log file down to a reasonable size.
Viewers will learn how the fundamental information of how to create a table.
Suggested Courses

577 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question