Home Forums SQLServerCentral.com Editorials Checking CHECKDB RE: Checking CHECKDB

  • May 23, 2018 at 12:22 pm

    #1991686

    Steve Jones - SSC Editor - Wednesday, May 23, 2018 8:54 AM

    Eric M Russell - Tuesday, May 22, 2018 2:12 PM

    I don't see the point in transferring results. The online database and the restored copy are two different instances. Just because one is checks out ok, the other could still be bad.

    Potentially, but a backup of the database is a valid way to run checkdb, especially when you can't spare resources on the online database. Since in this case, many times people use a dedicated server to check many databases, the restored copy isn't maintained. It's dropped. Capturing that information would be helpful for monitoring to know if dbcc has been run for a particular database.

    It's good practice to test our backups, so it would make sense to automate the process of: backup from server A, restore to server B, run checkdb on server B, and then also keep server B online to miscellaneous reporting. In a sense, dbcc checkdb is a heavy duty data validation and reporting process that should be offloaded from server A if possible. But, it's just the point about copying the results of the database check on server B back to server A that I'm not sure about.

    "Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho