That was the issue.  There is a big difference between logging activity - which is what the error logs are doing - and logging transactions - which is what is happening on your database server.

Now - the important thing is - that you understand the ramifications of the change you just made.

By effectively turning off transaction logging (when you switch to simple) you have lost the ability for a point in time recovery.

So what that means is, in the case of a need to restore the database, you'll be able to go back to your last good full backup, plus any differentials - but you won't be able to restore to 11:20 am on March 28th.

Most likely, you'll be okay, as you'll look for the recycle bin to help you there - but just want to be sure you know the ramifications of the change.

The alternative is to change the recovery mode back to what it was - and then add in some transaction log backups.  Once a transaction log is backed up, you can truncate it - which will shrink it back to the 500k.

Pingback from  SharePoint 2007 Link Love: 03-06-2008 at  Virtual Generations

Great help, thanks

Why wouldn't this reset after a full backup, we backup weekly but this files has been growing and growing for a year.