Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
venkath
Posting Yak Master
202 Posts |
 Posted - 2008-03-10 : 04:26:39
|
| Could one of you please explain to me why the transaction log file backups on one of our production database average about 30MB in file size once an hour? These seems really large for these databases as the size of the database is something like 64MB. Plus, how come the transaction log file backups never fluctuate in size during peak and off-peak hours? So I would think that the transaction log file backups should be much smaller during night time when there is little if any activity, correct?I'd really like to understand this so I'm looking forward to it. |
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-03-10 : 11:57:37
|
| Transaction log backup not only captures new records but it also captures updated and deleted records. |
 |
|
|
xgirl
Starting Member
6 Posts |
Posted - 2008-03-10 : 14:37:21
|
| What about the space used? Backing up the trans log will not shrink the file size but drops the committed transactions. Allow the trans log to change size use dbcc shrinkfile. That being stated, monitor the translog file used space because shrinking and growing the translog will cause fragmentation of the log file. This may impact performance. |
|
|
|
|
|
|
Transactional log backup size is not changing.