Re: DBCC CheckDB

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Andrew J. Kelly (sqlmvpnooospam_at_shadhawk.com)
Date: 09/24/04 

Date: Fri, 24 Sep 2004 17:34:35 -0400

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

Relevant Pages

  • Re: DBCC CHECKDB Errors
    ... Here's a start if you have corruption of a suspect database: ... "Prasad Koukuntla" wrote in message ... I got the following errors when I ran the DBCC Checkdb on my ... However, I am already running SQL SERVER SP3, ...
    (microsoft.public.sqlserver.server)
  • Re: Attempt to fetch logical page
    ... You have a corruption in your database. ... Second, if you are on SQL Server 2000, check the specific recommendations for your error. ... This error occurs when Microsoft® SQL ServerT detects database corruption. ... execute DBCC CHECKDB to determine the extent of the damage. ...
    (microsoft.public.sqlserver.server)
  • Re: DBCC CHECKDB WITH DATA_PURITY on production
    ... You need to run the dbcc checkdb with data purity only if the database ... If the database is created on SQL ... For databases created in SQL Server 2005 and later, column-value integrity ...
    (microsoft.public.sqlserver.server)
  • Re: Options for repairing a database
    ... None of the articles however tell me whether I would have been unable to do anything else given that DBCC CHECKDB was reporting an "unrepairable error". ... At that point we couldn't go any further even if we did want to allow data loss and so gave up on repairing the database and wen't back to backups. ... The only tool that I know of for doing repairs is the DBCC tool but I was wondering if there were any other tools that could have helped us get the data out? ...
    (microsoft.public.sqlserver.server)
  • Re: Problem SQL 6.5
    ... In SQL 6.5 the error 605 it is very hard to solve, Execute DBCC CHECKDB on ... the database and identify the table got corrupted. ... Script out the indexes of that table. ... rename the original table to tablename_old ...
    (microsoft.public.sqlserver.server)