Change initial sixe of transaction log file

  • Dear All

    We have a db with Full recovery Model. Daily full backup is taken and every hour transaction back up is taken.

    Full back up file size is 8GB and trnasction log back up is 7GB ( imidiatly after full back up) , later transaction back ups are 2MB. And this is almost the same every day.

    Noticed that the initial size of the transaction log is Approximatly 7GB. Is this the reason why the trnasction backup file size is 7GB?

    If yes then how do i change the initial log file size?

    I have to do it on the live server. Please guide

    Regards

  • Dear All

    After shriking DB initial size changed.

  • Krishna1 (11/13/2013)


    Noticed that the initial size of the transaction log is Approximatly 7GB. Is this the reason why the trnasction backup file size is 7GB?

    Setting appropriate initial size is good from performance perspective because it make the transactions slow whenver file needs the growth or expansion so we should always consider the initial size based on the data/transaction growth.

    -------Bhuvnesh----------
    I work only to learn Sql Server...though my company pays me for getting their stuff done;-)

  • why the initial size keeps changing?

  • Krishna1 (11/18/2013)


    why the initial size keeps changing?

    Either MODEL db initial size or somebody (externally)intentionally doing this.

    -------Bhuvnesh----------
    I work only to learn Sql Server...though my company pays me for getting their stuff done;-)

  • Krishna1 (11/14/2013)


    Dear All

    After shriking DB initial size changed.

    Shrinking DB is different from Shrinking a File. You could have shrunk only the log file.

    Shrink usually introduces a lot of fragmentation.

    You're lucky your database is small.

    Regards,

    IgorMi

    Igor Micev,My blog: www.igormicev.com

  • Krishna1 (11/18/2013)


    why the initial size keeps changing?

    Most database actions are being logged, hence stored in the LOG file. The LOG file will grow when actions are being executed on the database and the current free size inside the file is not enough. In full recovery mode the space in the LOG file can only be re-used when 1. the action is completed and 2. a LOG backup is taken.

    It looks like in your environment a large action (like ETL load or large update) or many small actions are being executed causing the LOG file to grow.

    Check if you take regular LOG backups throughout the whole day and not only during working hours!

    ** Don't mistake the ‘stupidity of the crowd’ for the ‘wisdom of the group’! **

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

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