Jaros³aw Kozik (jkozik (AT) op (DOT) pl) writes:
Why did it become suspect in the first place?

This is not a situation that is easy to assist with over the net, since
a lot of information may be neeeded. A database can become suspect because
of lack of disk space, because of corruption etc.

Search for "suspect" in Books Online, and see if any of the topic you
find seem to apply to your situation. Else I would recommend you to open
a case with Microsoft, at least if this a production database that would
be costly to lose.


--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx

I think, my database is strong corupted. Becouse when I try to connect
database to server I see MSServer error 9004.

I dont konow how rebuild it .


regards IJKK


Uzytkownik "Erland Sommarskog" <esquel (AT) sommarskog (DOT) se> napisal w wiadomosci
news:Xns993359BB9159Yazorman (AT) 127 (DOT) 0.0.1...

Jaroslaw Kozik (jkozik (AT) op (DOT) pl) writes:
Error 9004: "An error occurred while processing the log for database
'%.*ls'." Seems like your log file is hosed.

If you have a recent backup of the database, restore it.

If you don't have a backup, there may be a possibility to recover the
database to some extent, but it is far from certain. Assuming that a
hardware problem thrashed the log file, it could have hit the data
file as well, if the data file is on the same disk. And there is a very
clear risk that there are one or more unrecovered and incomplete
transactions in the database. This means that once you are able to
access it, you may find corruption and/or inconsistences in your data.

If you want to know the steps to do this, please drop me a mail. I don't
want to post this on the newsgroups, because these are commands that
could cause damage if you don't know exactly what you are doing.

Also, you should examine why the log file became corrupted. This could
be a hardware issue, such a faulty disk or a bad memory board.

--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx