Prev: Auto update statistics versus manual statistics update
Next: FTS: can I find texts not containing a specified word?
From: Benn on 1 Mar 2010 01:22
Hi,

I have a corrupt MS SQL Server 2005 database which I
am trying to repair using:

DBCC CHECKDB ('MYDB', REPAIR_ALLOW_DATA_LOSS)

Unfortunately this does not seem to fix anything.
After running the repair multiple times, I ran

DBCC CHECKDB ('MYDB') WITH NO_INFOMSGS

to see if it fixed the corruption, I noticed that is was returning a
random amount of errors on each run.
Does any know if It is the case that this database is beyond repair?
If so will the best approach be to revert back to a non corrupt
database backup and then roll forward using Transaction Logs?

thanks in advance.
From: Uri Dimant on 1 Mar 2010 02:51
Benn
Start reading http://www.sqlskills.com/BLOGS/PAUL/category/Corruption.aspx


"Benn" <bennblum(a)gmail.com> wrote in message
news:af96b6a7-6d22-40b6-9b14-bf43aff9c4b6(a)u5g2000prd.googlegroups.com...
> Hi,
>
> I have a corrupt MS SQL Server 2005 database which I
> am trying to repair using:
>
> DBCC CHECKDB ('MYDB', REPAIR_ALLOW_DATA_LOSS)
>
> Unfortunately this does not seem to fix anything.
> After running the repair multiple times, I ran
>
> DBCC CHECKDB ('MYDB') WITH NO_INFOMSGS
>
> to see if it fixed the corruption, I noticed that is was returning a
> random amount of errors on each run.
> Does any know if It is the case that this database is beyond repair?
> If so will the best approach be to revert back to a non corrupt
> database backup and then roll forward using Transaction Logs?
>
> thanks in advance.


 | 
Pages: 1
Prev: Auto update statistics versus manual statistics update
Next: FTS: can I find texts not containing a specified word?