Hello, We had a db with a ballooned transaction log. Full db backups didn't reduce the size nor did transaction log backups. Finally we tried backing up the log with the truncate_only option and that did reduce size dramatically.
But I have read that this should only be done in emergency situations.
So what is the best/safest way to magage this log file? Shouldn't full backups truncate the log removing inactive portions? I suspect the app is in need of tweaking so it doesn't fill the log file with junk.

Any help is greatly appreciated! Thanks, Morrisos