no, no new harddrives. I did have a stored procedure that attempted to BCP a non existant file into the database. Could that have done it? How can I recover it??? (Or can I?)
Main Topics
Browse All Topicsanyone know why a) how to recover a database markedt suspect and b) why a database becomes marked suspect
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
I've herd this can help:
isql -Usa -P
1> sp_configure allow, 1
2> go
1> reconfigure with override
2> go
1> begin tran
2> update sysdatabases set status = -32768 where name = 'suspect_db'
3> go
(should report 1 row affected at this point. If it reports that
more than 1 row was affected, do not commit the transaction in the next
step. Exit isql ad try it again, or use abort tran)
1> commit tran
2> go
1> exit
2> go
RESTART MSSQL SERVER
1> use suspect_db
2> go
1> checkpoint
2> go
1> exit
2> go
$RESTART SERVER
1>begin tran
2> update sysdatabases set status = 0 where name = 'suspect_db'
3>go
(should report 1 row affected at this point. If it reports that
more than 1 row was affected, do not commit the transaction in the next
step. Exit isql ad try it again, or use abort tran and try again)
1> commit tran
2> go
1> exit2> go
$RESTART SERVER
It is now a good idea to run the following two dbcc commands
1> dbcc checkalloc (suspect_db, fix)
2> go
1> dbcc checkdb (suspect_db)
2> go
Business Accounts
Answer for Membership
by: simoraikovPosted on 1999-05-13 at 08:29:33ID: 1095061
Have you added a ne harddrive or something like that