Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!feeder2.ecngs.de!ecngs!feeder.ecngs.de!Xl.tags.giganews.com!border1.nntp.ams.giganews.com!nntp.giganews.com!local2.nntp.ams.giganews.com!nntp.bt.com!news.bt.com.POSTED!not-for-mail NNTP-Posting-Date: Tue, 30 Oct 2012 16:43:21 -0500 From: "Cathy" Newsgroups: comp.databases.ms-sqlserver References: <0tudnXZbkNzRyxHNnZ2dnUVZ7qednZ2d@bt.com> <17CdnaWZsLRDOBDNnZ2dnUVZ8s-dnZ2d@bt.com> In-Reply-To: Subject: Re: SIMPLE Recovery Model Log file growth Date: Tue, 30 Oct 2012 21:43:18 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="Windows-1252"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Windows Mail 6.0.6002.18197 X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6002.18463 Message-ID: Lines: 22 X-Usenet-Provider: http://www.giganews.com X-AuthenticatedUsername: NoAuthUser X-Trace: sv3-JWfPrwxMFPp1bZAR1p1zr0xinJpisI/B22CmiFgPYKgsW8TKYMoSYX8IMyfR59tpy4E7Jimv3NJ75kT!jwUFO8gEBR4NaFn7p1IvtAb+PHFbUY7exn4L7pbbQeo41sT1MVFCnHfFdDiTKonQtcwiI4xFudI3!1w== X-Complaints-To: abuse@btinternet.com X-DMCA-Complaints-To: abuse@btinternet.com X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.40 X-Original-Bytes: 2190 Xref: csiph.com comp.databases.ms-sqlserver:1345 Perhaps I am confusing the issue by providing too much details and getting things sidetracked Lets forget about how many files there are and how many databases. My question is as before what is the simplest to 1. close any open transactions in the log file 2. take it offline if needed 3. Truncate it if needed 4. Shrink the database (sorry I realise my error now saying logfile before) 5. backup the database 6. bring the database online again Imagine this is one database (whether simple of full recovery model) I am hoping for a single TSQL Script I can use regards C