Results 1 to 4 of 4
  1. #1
    Join Date
    Feb 2004
    Posts
    2

    Post Unanswered: Log Shipping Transaction Logs.

    Hi,

    We currently have a couple a large Databases running on SQL 2000 SP3 Clustered Windows 2000 SP3 environment.

    Log Shipping is enabled for both databases shipping to a Standalone SQL 2000 SP3 Windows 2000 SP3 box.

    Log Shipping occurs every 15 mins with the Transaction Files on average being no more than 500KB in size. However, every now and then a Transaction Log comes through and it can be as big as 3.52GB.

    Not sure why this is happening. Anyone got any ideas?

    Regards

    Paul Towler

  2. #2
    Join Date
    Oct 2001
    Location
    Naples, FL
    Posts
    273
    Is this after substantial activity or reindexing?
    ---------------
    Ray Higdon MCSE, MCDBA, CCNA

  3. #3
    Join Date
    Feb 2004
    Location
    india
    Posts
    67
    i think auto shrink or some other job is enabled
    if iam right, the auto shrink or job gets activated and the step goes thru
    which will obviously create transaction file with huge size.

  4. #4
    Join Date
    Feb 2004
    Posts
    2

    Thumbs up

    Thanks for your replies.

    There is a Job to Optimise the Database which does re-index the database. I presume all the indexing changes count as changes and therefore shipped as one big Transacton file.

    Hopefully there is a way to prevent these hugh Transaction Files without turning off the indexing job.

    Regards
    Paul Towler

Posting Permissions

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