Preventing MS SQL Transaction log bloat

The easy solution to this is:

1. make a backup of your transaction log
2. shrink your transaction log

Do not ever use "truncate_only" or "no_log" unless you wish to forget about the whole "database recovering in any point of time".

See some links here:

• http://msdn.microsoft.com/en-us/library/ms190440.aspx
• http://vikasrajput.wordpress.com/2010/08/07/sql-server-logfile-getting-too-big-or-not-getting-truncated/
• http://www.sqlskills.com/blogs/paul/post/backup-log-with-no_log-use-abuse-and-undocumented-trace-flags-to-stop-it.aspx