Hey Folks,

According to the documentation (BOL), the best way to remove inconsistencies
in a database that fails dbbcc checkdb is to do a restore. I did this and the
inconsistency still exists (CHECKDB found 0 allocation errors and 1
consistency errors in database). Short of running the repair with the
Allow_Data_Loss option, is there anything else you can suggest?

From an internals perspective, I'd like to learn more about this issue.
Wouldn't mind a good technical whitepaper on the subject. BOL is somewhat
vague in the explanation.
--
Thanks,

Scott H.

A restore will bring back the database as it looked like when you performed the backup. I.e., you
need to find a backup from when the database was clean. 2005 outputs to errorlog file on each
startup when you last did a *clean* checkdb for each database.

Google for Paul Randal. He is the authority on this subject, and make sure you find both his blog
from MS as well as SQLSkills. Also, the most recent SQL Server book from Ken Henderson has some good
info on this (among other things).

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi


"Scott H." <ScottH@discussions.microsoft.com> wrote in message
news:8146E754-EA42-43B6-8591-82FD5DB4F056@microsoft.com...
> Hey Folks,
>
> According to the documentation (BOL), the best way to remove inconsistencies
> in a database that fails dbbcc checkdb is to do a restore. I did this and the
> inconsistency still exists (CHECKDB found 0 allocation errors and 1
> consistency errors in database). Short of running the repair with the
> Allow_Data_Loss option, is there anything else you can suggest?
>
> From an internals perspective, I'd like to learn more about this issue.
> Wouldn't mind a good technical whitepaper on the subject. BOL is somewhat
> vague in the explanation.
> --
> Thanks,
>
> Scott H.

Tibor Karaszi wrote:
> A restore will bring back the database as it looked like when you
> performed the backup. I.e., you need to find a backup from when the
> database was clean. 2005 outputs to errorlog file on each startup when
> you last did a *clean* checkdb for each database.
>
> Google for Paul Randal. He is the authority on this subject, and make
> sure you find both his blog from MS as well as SQLSkills. Also, the most
> recent SQL Server book from Ken Henderson has some good info on this
> (among other things).
>

Paul's blog can be found at: http://www.sqlskills.com/blogs/paul/

BTW, his presentation at TechEd this past week was excellent. He showed
how to not only survive, but in a lot of cases do so without any data loss.

Jeff