DBCC CheckDB

Another question from the new Admin on the block.
I read in the docs that as of SQL7 dbccs are not required as part of your
backup plan. The servers I just inherited are not running any database
integrity checks at any time.
Should checks still be run occasionally.
Thanks!
Mike Lackey
Database Adminstration
Sybase/Oracle and recently back to MSSQL
They are never required but a good idea. The idea behind a DBCC CHECKDB is
to ensure (mostly) physical integrity of your database objects. While it is
true there is not as much a problem with 7.0 and 2000 like there was with
6.5 it can still happen. Mainly hardware related issues caused problems
that this checks. The sooner you find out there is a problem the best
chance you have of not loosing valuable data. So while it is not required
it is recommended. How often depends mainly on how often you can afford to
run it etc.
Andrew J. Kelly SQL MVP
"Mike Lackey" <MikeLackey@.discussions.microsoft.com> wrote in message
news:C11410C3-6891-486C-A375-CC51E42FE0EA@.microsoft.com...
> Another question from the new Admin on the block.
> I read in the docs that as of SQL7 dbccs are not required as part of your
> backup plan. The servers I just inherited are not running any database
> integrity checks at any time.
> Should checks still be run occasionally.
> Thanks!
> --
> Mike Lackey
> Database Adminstration
> Sybase/Oracle and recently back to MSSQL
|||Hi,
I agree with Andrew. I recommend you to run the DBCC CHECKDB atleast once a
week. By this you can always ensure that your data is in good shape.
Thanks
Hari
MCDBA
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:esgBN5noEHA.2340@.TK2MSFTNGP11.phx.gbl...
> They are never required but a good idea. The idea behind a DBCC CHECKDB
> is
> to ensure (mostly) physical integrity of your database objects. While it
> is
> true there is not as much a problem with 7.0 and 2000 like there was with
> 6.5 it can still happen. Mainly hardware related issues caused problems
> that this checks. The sooner you find out there is a problem the best
> chance you have of not loosing valuable data. So while it is not required
> it is recommended. How often depends mainly on how often you can afford
> to
> run it etc.
> --
> Andrew J. Kelly SQL MVP
>
> "Mike Lackey" <MikeLackey@.discussions.microsoft.com> wrote in message
> news:C11410C3-6891-486C-A375-CC51E42FE0EA@.microsoft.com...
>