"Hilary Cotter" wrote:

> try
> update sysdatabases
> set status = status & ~256
> where name = 'databasename'
>
> or
>
> update sysdatabases
> set status = status | -32768
> where name = 'databasename'
>
> after this restart SQL Server and you should be able to access the database
> to bcp the data out.
>
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
>
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
>
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
>
>
> "Brandon" <Brandon@discussions.microsoft.com> wrote in message
> news:2E42F3B7-581C-495F-B963-3207E63757D0@microsoft.com...
> > We've got database marked as "suspect" in our MSSQL Server. We found out
> > this
> > when viewing it using Enterprise Manager. We are ready to forsake the
> > unwritten transactions in the transaction log. Please tell us what we
> > should
> > do so that we can bring the database marked as normal.
> >
> > We tried to detach the "Suspect" database and got error. We restarted
> > MSSQL
> > and those databases got detached successfully. But when we tried to attach
> > the database back to the MSSQL Server, we got the error screen. The error
> > is
> > also Please tell us how we can attach the database back to MSSQL Server
> > again.
>
>