Results 1 to 5 of 5
  1. #1
    Join Date
    Jul 2003
    Location
    Penang, Malaysia
    Posts
    212

    Unanswered: Transaction Log Growth Rate

    I read somewhere that limiting the growth percentage of the transaction log to small values aren't so good.

    This is because with each growth, it will create even more "virtual logs".
    And having more virtual logs will slow down overall performance and backup processing.

    So, as a consencus base on this findings, can someone give comments on the recommended growth rate of a transact log?

    You can give me like something :

    Transaction Log growth rate base on 5% of DB.
    If DB=50MB , Initial Log Size =2.5 , Growth rate=2.5%

    So what is the best practice estimation? Please give your comments.
    Patrick Chua
    LBMS ( Learn By My Self) NPQ ( No paper Qualification )

  2. #2
    Join Date
    Nov 2002
    Location
    Jersey
    Posts
    10,322

    Re: Transaction Log Growth Rate

    It depends...how many transaction do get during a day?

    You you project the growth of the database over time?

    The reason they same a small % is bad, because have allocate more often, causing additional overhead, as compared overhead less frequently...

    And do you have it set to unrestricted growth?
    Brett
    8-)

    It's a Great Day for America everybody!

    dbforums Yak CorralRadio 'Rita
    dbForums Member List
    I'm Good Once as I ever was

    The physical order of data in a database has no meaning.

  3. #3
    Join Date
    Jul 2003
    Location
    Penang, Malaysia
    Posts
    212
    Thanks for u'r comments,
    Yeah, I know it depends, so what's u'r way of doing it? What attributes do you take into account for consideration b4 u judge the size of u'r initial trasact log and its growth rate.....any mathematical formula to follow??


    anyone?
    Patrick Chua
    LBMS ( Learn By My Self) NPQ ( No paper Qualification )

  4. #4
    Join Date
    Jul 2003
    Location
    Penang, Malaysia
    Posts
    212
    Please, some other comments from the forum members?
    Patrick Chua
    LBMS ( Learn By My Self) NPQ ( No paper Qualification )

  5. #5
    Join Date
    Oct 2003
    Posts
    706

    Wink

    Unfortunately there is no great answer. The transaction log is the bane of the SyBase/MSSQL design. The best thing to do is simply to allocate one very large contiguous area for it (don't do small percentages because that just creates a propagation of individual files), and clear it out periodically using some automatic scheduler.

    The overflow-space is needed so that the server does not "utterly stop cold" but your log-space should be large enough so that this never occurs in practice.

    The transaction-log is one reason why I rarely use MS-SQL in new designs, but that's "neither here nor there." Certainly it is very refreshing to work with a server that doesn't use one.
    ChimneySweep(R): fast, automatic
    table repair at a click of the
    mouse! http://www.sundialservices.com

Posting Permissions

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