Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

How can a db get marked as SUSPECT?

0 views
Skip to first unread message

Steve Schoon

unread,
Dec 12, 1997, 3:00:00 AM12/12/97
to

Does anyone know any specific ways a db can become marked as SUSPECT?
I've had this happen a lot recently (twice today, to different clients)
and I'd love to solve it.

Platform is:

Compaq 800 Pentium Pro 200
80meg ram
4gig disk
Sql Server 6.0 SP3 (<-bummer, not at 6.5 yet)

Thanks for any and all ideas.

Steve Schoon
email: Remove nospam. from reply address

Neil Pike

unread,
Dec 13, 1997, 3:00:00 AM12/13/97
to

Steve - there are many ways, but the errorlog file always tells you why
it's been marked suspect. - e.g. failed recovery, can't open file etc.
You need to post the diagnostic info that SQL gives you.

Neil Pike MVP/MCSE
Protech Computing Ltd (MS Solution Provider)

Steve Schoon

unread,
Dec 15, 1997, 3:00:00 AM12/15/97
to

In article <VA.000003a...@neilpikeport.itops.natwestuk>,
10057...@compuserve.com says...
Yeah, dumb of me not to post that stuff. Well, now the errorlog has been
overwritten, so I don't have it. Next time....

I've seen db's become marked as suspect because the machine was powered
off w/o shutting it down cleanly, but I was looking for more possible
reasons.

--

Dimitry Ioffe

unread,
Dec 18, 1997, 3:00:00 AM12/18/97
to

Steve,
DB will become a suspect due to a failure of write (usually) to the
database. One can reverse bits and 6.5 has a stored proc to do that.

-Dimitry.


On Fri, 12 Dec 1997 15:47:29 -0500,
steve_...@nospam.spartanstore.com (Steve Schoon) wrote:

>Does anyone know any specific ways a db can become marked as SUSPECT?
>I've had this happen a lot recently (twice today, to different clients)
>and I'd love to solve it.
>
>Platform is:
>
>Compaq 800 Pentium Pro 200
>80meg ram
>4gig disk
>Sql Server 6.0 SP3 (<-bummer, not at 6.5 yet)
>
>Thanks for any and all ideas.
>

0 new messages