Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Change initial sixe of transaction log file Expand / Collapse
Author
Message
Posted Wednesday, November 13, 2013 10:28 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Sunday, April 27, 2014 7:55 PM
Points: 218, Visits: 556
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


Post #1514145
Posted Thursday, November 14, 2013 2:15 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Sunday, April 27, 2014 7:55 PM
Points: 218, Visits: 556
Dear All

After shriking DB initial size changed.
Post #1514174
Posted Thursday, November 14, 2013 6:34 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Tuesday, August 19, 2014 12:26 AM
Points: 2,840, Visits: 3,963
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
Post #1514248
Posted Monday, November 18, 2013 12:43 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Sunday, April 27, 2014 7:55 PM
Points: 218, Visits: 556
why the initial size keeps changing?
Post #1515113
Posted Tuesday, November 19, 2013 3:48 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Tuesday, August 19, 2014 12:26 AM
Points: 2,840, Visits: 3,963
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
Post #1515481
Posted Tuesday, November 19, 2013 4:25 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Yesterday @ 11:26 PM
Points: 2,929, Visits: 2,947
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,
SQL Server developer at Seavus
www.seavus.com
Post #1515492
Posted Tuesday, November 19, 2013 5:19 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Yesterday @ 3:13 PM
Points: 2,255, Visits: 2,718
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’! **
Post #1515502
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse