December 21, 2012 at 1:20 pm
"There's still a widely held misconception that when properly in the FULL or BULK_LOGGED recovery models that full or differential backups can truncate the log. No. It *NEVER* happens. This is one of the reasons why I'm doing a whole spotlight session on this at PASS this year - the transaction log and its behavior is IMHO one of the most misunderstood parts of SQL Server. "
.
December 21, 2012 at 1:22 pm
Sorry SSCoach, I'm sure you can give a much better answer than a link to an article, but I found this link rather useful in understanding what all is going on. If it's a lightly used server and data doesnt need to be up to the minute at all times, I would say run it every 4-6 hours. It will only be as big as what it did, so there's not space savings for lots of little transaction log backups vs fewer large transaction log backup, just limiting the data loss and complexity of the restore. Mind you, you still need to back up the tail of the log on a failed database if you can. *correct me if i'm wrong*
.
December 21, 2012 at 1:40 pm
David92595 (12/21/2012)
@SSCoachCan you please provide a resource that shows that full backups do not truncate transation logs? I was under the impression that a full backup does truncate the transation logs.
It's not that I don't believe you, but I will need some evidence to provide to my superior if I am going to start using transation log backups...
Thank you,
David92595
First, look at Books Online, BACKUP DATABASE. I would also read the the last article I have referenced below in my signature block about Managing Transaction Logs. The link provided by fluffydeadangel is also a good one.
December 21, 2012 at 3:21 pm
I will look into the links provided.
Thank you all for your assistance,
David92595
Viewing 4 posts - 16 through 18 (of 18 total)
You must be logged in to reply to this topic. Login to reply