Post reply

will maintenance tasks like(checkdb,index rebuild,statsupdate) and shrink file also run on the secondary database.

  • August 16, 2010 at 6:40 am

    #227944

    HI,

    On my databases there are some weekly maintenance tasks like (checkdb,index rebuild,statsupdate) and we will shrink log files when space issues occur. Now we are planning to implement mirroring on some databases and logshipping on some databases.So we are worrying that

    1.whether these maintenance tasks(checkdb,index rebuild,statsupdate) and shrink file will rerun on the secondary database in logshipping or not.

    2.whether these maintenance tasks(checkdb,index rebuild,statsupdate) and shrink file will rerun on the mirrored database in database mirroring or not.

    Please advice me on this.

    Thanks,

    Vamsy

  • August 16, 2010 at 6:43 am

    #1207307

    My databases are in sqlserver 2005 and 2008

    Thanks,

    Vamsy

  • August 16, 2010 at 7:51 am

    #1207350

    jobs are in msdb database so as long you not restore msdb, its not gonna affect secondary server.

    Also just a suggestion, instead of scheduling the shrink log file, you should increase the full/log backup frequency.

    ----------
    Ashish

  • August 16, 2010 at 8:02 am

    #1207361

    Vamsy

    Since the operations you mention are fully logged, I would say that doing one of them on the source database would also do it on the target. That's just an educated guess, though - I'm sure the information is out there if you search for it!

    John

  • August 16, 2010 at 8:23 am

    #1207380

    both mirroring log shipping are replaying all transactions on the secondary, so if it CHANGES data that is held in the primary database, it has the same affect on the secondary.

    Integrity checks are read only processes, so would not be replayed, also as corruptions are generally caused at the disk level, a corruption that occurs on the primary will not be copied over to the secondary if the log was not affected, and it is feasible for the secondary to be corrupted independent of the primary.

    ---------------------------------------------------------------------

  • August 17, 2010 at 2:40 am

    #1207696

    Thanks for your replies............

    1.Integrity checks(check db)--------won't be done on the secondary database in case of logshipping and mirroring

    2.Maintenance tasks(index rebuilds) ---will be done on the secondary database in case of logshipping and mirroring

    3.shrink file -------------will be done on the secondary database in case of logshipping and mirroring

    These are results............If anything of the above is wrong please suggest me with some explanations......

    Thanks,

    Vamsy

  • August 17, 2010 at 6:39 am

    #1207820

    vamshikrishnaeee (8/17/2010)

    3.shrink file -------------

    This should be a one time operation, don't make a routine of it!

    If your files continuously grow to these sizes maybe you should increase your disk space to cope of revisit your recovery models\backup frequencies!

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

Viewing 7 posts - 1 through 6 (of 6 total)

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