I don't recommend removing them unless you want to cause yourself some major hassle.
Even with 'simple' recovery model, you need logs. For ACID, you have to keep log information that goes back as far as your oldest transaction. Now, you should be able to shrink those logs (from the GUI) in order to recover most of their space - but you still have to have logs. This is just like circular logging for Exchange. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Oliver Marshall [mailto:[email protected]] Sent: Wednesday, January 26, 2011 5:11 AM To: NT System Admin Issues Subject: SQL LDF files and simple databases Hi, We have a folder chock full of old LDF files. We changed our databases to a simple recovery model some time ago as we use image based backups every few mins, so we wanted to save space by removing the need for the logs. The LDF files weren't removed at the time. I've just gone to remove them and noticed that the last modified time/date stamp on all of them is a few days ago, despite the DBs being made simple many months back. I've checked all the DBs and all of them on this box are set to Simple. Any ideas why SQL server would still modifying the LDF files? I'm a bit cautious about removing them now that something is clearly modifying them. Olly ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
