Post reply

Prevent the transaction log files from growing unexpectedly

  • February 20, 2006 at 3:30 pm

    #111693

    I'm reading this Knowledge Base below is the link:

    http://support.microsoft.com/?kbid=873235

    Mention there:

    To prevent the transaction log files from growing unexpectedly, consider using one of the following methods:

     

    •

    Configure the automatic expansion of transaction log files by using memory units instead of a percentage after you thoroughly evaluate the optimum memory size.

     

    Anyone know this? how to configure?

  • February 20, 2006 at 3:38 pm

    #622128

    Scheduling the log backups frequently should log file size in check..

    To congifure the log file to grow in MB's instead of percent...

    Enterprise Manager->Database Properties->Transaction Log-> Auto Grow file->In MegaBytes... or you cna do the same using T-SQL using alter database stmt..

     

     

    -Krishnan

  • February 21, 2006 at 10:50 am

    #622384

    Here's a T-SQL example using tempdb:

     alter database tempdb modify file

      (name = templog,

      size = 512MB,

      maxsize = 1025MB,

      filegrowth = 256MB)

     go

     checkpoint

     go

    RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."

  • February 21, 2006 at 2:31 pm

    #622458

    You have to read the source. The quote from the link has another link right after it in the article. This second link is to

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

    which in turn has a lot of recommendations and  "how to"s including:

    "...The exact value to use in your configuration setting and the choice between a percentage growth and a specific MB size growth depends on many factors in your environment. A general rule of thumb to you can use for testing is to set your autogrow setting to about one-eight the size of the file..."

    What I don't understand and it is probably a typo in the original link and the original question it says "prevent transaction log from growing unexpectedly..." Well, whatever it is, MB or % , it will grow anyway, not prevent from growing, unless as Rudy says, you specify the MAXSIZE. But than you may prevent your database from accepting any inserts or updates with the messages that the log is full.

    Regards,Yelena Varsha

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

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