Overgrown transactional log files can turn into real problems if they are not handled properly. Today SQL Server consultant Tim Chapman discusses the perils of not handling SQL Server log growth ...

SQL Server keeps a buffer of all of the changes to data for performance reasons. It writes items to the transaction log immediately, but does not write changes to the data file immediately.

Log files can be damaged due to malware or virus attacks on the system hosting the SQL server; If the SQL Server account permissions and configuration are modified incorrectly, it can impact the log ...

One extra note, if you do log to a flat file and there are no errors, ... He is also the President of the Colorado Springs SQL Server User Group. He can be contacted at www.consortioservices.com.