Results 1 to 5 of 5

Thread: Dbcc Checkdb

  1. #1
    Join Date
    Dec 2002
    Posts
    1,245

    Unanswered: Dbcc Checkdb

    How often do you run it in your shop?

    I'm seeing (from the new SQL Best Practices Analyzer) that MS recommends that it be done once every two weeks on SQL 2005.

    I have never been in the habit of running it in production. I have never experienced database corruption in any form.

    Just curious.

    Regards,

    hmscott
    Have you hugged your backup today?

  2. #2
    Join Date
    Nov 2004
    Location
    on the wrong server
    Posts
    8,835
    Provided Answers: 6
    here i run it every night on every database, but our databases are relatively small. In larger environments, I typically make it part of the Sunday night maintenance.

    corruption does happen. i had checkdb failing on one database once and the table it was failing on had more rows in it than was being returned by a SELECT * FROM. It was a small lookup table on a development server, so I just rebuilt it, but it was weird. You could see the rows in the EM but not by querying from the QA.
    “If one brings so much courage to this world the world has to kill them or break them, so of course it kills them. The world breaks every one and afterward many are strong at the broken places. But those that will not break it kills. It kills the very good and the very gentle and the very brave impartially. If you are none of these you can be sure it will kill you too but there will be no special hurry.” Earnest Hemingway, A Farewell To Arms.

  3. #3
    Join Date
    Jun 2007
    Location
    Ohio, USA
    Posts
    142
    Nightly, on ALL databases, ALL environments, including system DB's. The sproc also shoots out a nice big red-letter email if it finds anything. (I can post it here, or PM it to you, if you want to see it. I'm a horrible coder, but feel free to bend, fold, or mutilate it how you see fit.)

    If you don't want to run it in production, I'd recommend restoring some prod db's to another server, and running it there. I do that a lot, too.

    If you haven't seen it already, Paul Randal has a nice presentation online all about DB corruption best practices. Great stuff.

    http://www.microsoft.com/emea/itssho...px?videoid=549

    Good luck.

    -D.

  4. #4
    Join Date
    Feb 2004
    Location
    One Flump in One Place
    Posts
    14,912
    Quote Originally Posted by ReadySetStop
    If you don't want to run it in production, I'd recommend restoring some prod db's to another server, and running it there. I do that a lot, too.
    I believe this scores very highly on Best Practice as it tests your DR too.
    We don't do it here mind
    Testimonial:
    pootle flump
    ur codings are working excelent.

  5. #5
    Join Date
    Dec 2002
    Posts
    1,245
    Quote Originally Posted by ReadySetStop
    If you haven't seen it already, Paul Randal has a nice presentation online all about DB corruption best practices. Great stuff.

    http://www.microsoft.com/emea/itssho...px?videoid=549

    -D.
    Now THAT was a great presentation.

    Thank you for the link.

    Regards,

    hmscott
    Have you hugged your backup today?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •