Big TransactionLog and File-growth

  • 1) I have a SQL2K database I'm trying to support. The Transaction Log get out of control and grows very large. I guess this means I should be doing more timely Transaction Log backups?

    2) Regarding the database's Data File and Transaction Log file PROPERTIES. Both have "Automatically grow file" checked.

    On the Data File TAB, the "File Growth" is done with "By Percent" with 10%

    If I change that parameter to "In megabyes" with 10, it somehow changes back to "By Percent" with 10% !!!

    Is this a bug or is there someone else changing the parameter?

  • Do you make transaction log back ups? If you dont , then the log file is going to grow.

    Once you have the Transaction log back up done, you shouldnt have the problem of the log file getting big.

    -Roy

  • rew (1/26/2009)


    1) with 10, it somehow changes back to "By Percent" with 10% !!!

    Is this a bug or is there someone else changing the parameter?

    Not a bug that I've heard of. What version, and service pack are you running? And, as Roy stated, you should be backing up the T-Log to maintain control of the file size. All depends on business needs but if you're in full recovery mode, you should be doing it on a regular basis.

    -- You can't be late until you show up.

  • Just to complement what was already said, you should read the below articles to understand why its happenning and how can you avoid this.

    http://support.microsoft.com/kb/317375

    http://msdn.microsoft.com/en-us/library/ms345382.aspx

    [font="Courier New"]Sankar Reddy | http://SankarReddy.com/[/url][/font]

  • I currently run transaction log backups 4 times per day. I suppose I should increase this.

    The server is at SQL2K with sp4

    Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38 Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 2)

  • tosscrosby (1/26/2009)


    rew (1/26/2009)


    All depends on business needs

    The frequency is dependent on business needs. Hourly is good but does it meet your needs???

    -- You can't be late until you show up.

  • rew (1/26/2009)


    I currently run transaction log backups 4 times per day. I suppose I should increase this...

    I usually setup transaction log backups to run every 15 minutes, and sometime more often.

    It doesn't really cost more effort to do this; it's just a matter of changing the job schedule.

  • Thanks to all for the help!

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

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