Post reply

optimization job

  • October 20, 2008 at 9:46 am

    #77115

    we are using sql 2000. Each weekend, we will do optimization through database maintenance wizard, then it would generate over certain Gigb of transaction log, it would be shipped to our stand by server with log shipping. Since the log is so big, it easily fill up the space of the dr server, is this the way should be? what would be the good suggestion? thanks

  • October 20, 2008 at 10:18 pm

    #887410

    If you have to use log shipping, your scenario is normal. Otherwise, you may include DBCC SHRINKDB command in your optimization.

  • October 21, 2008 at 1:15 am

    #887451

    SQL ORACLE (10/20/2008)

    Otherwise, you may include DBCC SHRINKDB command in your optimization.

    If you don't mind the indexes been more fragmented afterwards than they were before the rebuild, then yes, you can do a shrink database.

    You can try bulk-logged recovery model for the duration of the rebuild. I think the log shipping will accept that, but please test before doing it in production. In bulk logged, the tran log won't get so big, however the log backups will still be large.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

Viewing 3 posts - 1 through 2 (of 2 total)

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