Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!eternal-september.org!feeder.eternal-september.org!mx04.eternal-september.org!.POSTED!not-for-mail From: Erland Sommarskog Newsgroups: comp.databases.ms-sqlserver Subject: Re: SIMPLE Recovery Model Log file growth Date: Sun, 28 Oct 2012 00:07:32 +0200 Organization: Erland Sommarskog Lines: 28 Message-ID: References: <0tudnXZbkNzRyxHNnZ2dnUVZ7qednZ2d@bt.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Injection-Info: mx04.eternal-september.org; posting-host="9c1143bfab35549403b85d70ea1a57d8"; logging-data="30070"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18NburZJYwX/o9MHjnyP9Yj" User-Agent: Xnews/2006.08.24 Mime-proxy/2.1.c.0 (Win32) Cancel-Lock: sha1:3rAhChuAbUFCSYW5IheSCuzxRA8= Xref: csiph.com comp.databases.ms-sqlserver:1337 Cathy (Cathy@Nospam.com) writes: > The database is used by Sharepoint but as we have no requirement to > restore to a point in time and will be happy to restore to the last > backup, (normally run in the middle of the night) > > I have noted that the log files are getting bigger and bigger and causing > disks to run out of space. > > My question is. what is the simplest way in which to close any open > transactions in the log file and truncate and shrink the file. You can use DBCC OPENTRAN to see if there are any open transactions in the database. Has the database ever been involved in replication? Replication also uses the log, and non-replicated transactions will cause the transaction to grow. And doublecheck that you really are in simple. -- Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se Links for SQL Server Books Online: SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx