Minimizing SQL transaction log file size on developer box running simple recovery model

Posted by Anders Rask on Server Fault See other posts from Server Fault or by Anders Rask
Published on 2011-02-24T09:49:04Z Indexed on 2011/02/24 15:26 UTC
Read the original article Hit count: 648

We have alot of SQL servers on development environment where we never take backup of the databases (TFS for code is enough).

The (SharePoint) databases are all set to simple recovery model, but the log files, especially for the SharePoint configuration database is growing quite large and filling up our data drive on the SQL server.

Since these log files are never used for anything, i would like advice on how to best minimize the size of these log files -or even disable them if possible.

I'm not completely sure why the log files grow so large even on simple logging (checked for long running transactions (DBCC OPENTRAN) but found none).

I guess the reason for the log files not being truncated is, that we dont take any backups, and hence Checkpoints arent reached.

The autogrowth for log files are set to autogrow by 10% restricted to 2 gb, so i guess that is why Checkpoint (70%) arent reached here either.

What would be the be best strategy to keep log files small (best case 0) without sacrificing performance (eg VLF fragmentation)?

© Server Fault or respective owner

Related posts about sql-server-2008

Related posts about log-files