Post reply

CHECK DB

  • September 27, 2011 at 5:44 am

    #244416

    Hi,

    Is it good practice/approach to restore the production database in test server and run the CHECKDB ?

    Thanks and Regards,

    Ravi.

  • September 27, 2011 at 5:49 am

    #1387049

    Yes absolutely , if you have the resources then this is the only sure-fire way of ensuring you have 100% clean backups.

  • September 27, 2011 at 5:58 am

    #1387056

    Thanks for your reply !!

    Running on the direct server shows any disk/page corruptions of real server. If run a test server, there wouldn't be satis-factory results, right ?

    I think, if you restore in the same server/production server and run checkdb..there would be we get good results.

    Please advise.

    Thanks and Regards,

    Ravi.

  • September 27, 2011 at 6:03 am

    #1387059

    No, if there is corruption on your live database, that corruption will be copied when you restore on to a different server. Restoring and running DBCC CHECKDB in this way is a valid way to check for corruption.

    John

  • September 27, 2011 at 6:04 am

    #1387060

    You can run checkDB on the production database. Just schedule it to run at an off peak time (weekends, nights, etc.).

    You would more likely use the restoration process to verify backups. Restoring a backup is the only real way of confirming they are consistent and error free, this can be accomplished on a test system and be fine.

    ______________________________________________________________________________________________
    Forum posting etiquette.[/url] Get your answers faster.

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply