http://blogs.msdn.com/jimmiet/archive/tags/Database+Logs/default.aspxTags: Database Logsen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/jimmiet/archive/2008/03/17/sharepoint-database-log-file-cancer.aspxTue, 18 Mar 2008 01:30:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:8297181jimmiet1http://blogs.msdn.com/jimmiet/comments/8297181.aspxhttp://blogs.msdn.com/jimmiet/commentrss.aspx?PostID=8297181&nbsp; <H1>SharePoint Database Log File Cancer</H1> <P>The database log files can grow like cancer, consuming large amounts of disk storage and impacting performance if not properly managed. This can be a particular problem for smaller deployments without dedicated DBAs or database experienced local administrators.</P> <P>The underlying issue is that native SharePoint backups do not backup the log files. Content databases are created with FULL recovery model if the System Model database has the FULL recovery model specified. This results in unbounded log file growth. It is not unusual for log files to grow to several times the size of the data files before someone notices the problem or worse yet, the log file consumes all available space such that the database server no longer responds. (view <A class="" title="SharePoint Database Log File Cancer" href="http://blogs.msdn.com/jimmiet/pages/sharepoint-database-log-file-cancer.aspx" mce_href="http://blogs.msdn.com/jimmiet/pages/sharepoint-database-log-file-cancer.aspx">entire article</A> ... )</P><img src="http://blogs.msdn.com/aggbug.aspx?PostID=8297181" width="1" height="1">Database LogsSharePoint