May 10, 2013 at 6:14 am
Hi,
I noticed several autogrowth events for the transaction log file of a database shortly after its backup job started. I've browsed around MSDN but can't find any mention of whether the transaction log is used for the backup operation.
Not a high-priority issue, just interested to know about it.
Thanks,
Jeff
May 10, 2013 at 6:50 am
The backup doesn't write to the transaction log, but while there's a backup in progress space in the log can't be reused. If you're seeing autogrow events, it suggests that maybe you need to grow the log a bit larger than what it is, leave space for cases like this.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
May 10, 2013 at 6:53 am
Thanks for replying and the info. I'll increase the log file as you've suggested.
~ Jeff
May 15, 2013 at 12:13 am
jhager, if you're interested, here is an article that explains why the transaction log is involved in full backups and how much of it is required:
http://www.sqlskills.com/blogs/paul/debunking-a-couple-of-myths-around-full-database-backups/[/url]
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
May 15, 2013 at 6:14 am
Thanks, I'm always interested to learn more about the product and its inner workings.
~ Jeff
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply