SharePoint University

Hello everyone, its my first post and I hope someone can help me!!

We have a single SharePoint 2007 server running and we are quickly running out of disk space. Friday we had about 20 gigs left, today, 1!! I am a newbie to sharepoint and sql also, please bear with me.

 I have searched and searched around on the server and it seems the only thing I see that is questionable is the following file:

WSS_Content_[a bunch of numbers and letters]_log.LDF

 This file is approx. 213 GB. Is this a "log" file that can be cleared out??? This is becoming a very urgent matter, I hope its an easy fix!!

 Thanks for any help guys.


 

Yes, this is a log file. It appears you have your recovery mode in bulk logged. This will cause that file to grow exponentially depending on how often the content of the database changes. I'm not a SQL expert, and this is a question I've been dying to ask anyway.

Can you change the recovery mode of a SharePoint database to Simple? What are the implications of doing so?

As for fixing your problem, I think a good backup of the database will reset the logs. Can anyone confirm that?

Okay, we are backing up the log file right now. Hope this helps or my phones going to start ringing! 

Well, sharepoint is still being backed up at the moment. Its pretty large, about 255 gb. If this option doesnt shrink the size of that logfile, what should my next option be? we've got about 600 MB left. Ive read a bunch of threads about shrinking it somehow but as I said before Im not a pro with sql and I dont want to start any problems.

 Thanks for helping guys.
 

Once you switch the backup method for the log file and do a backup, the log file should merge with the database and will strink considerably.

One easy way to prevent this in the future is to set your Recovery mode to simple for your SharePoint databases. However, this will mean you will heavily rely on your backups, and shouldn't rely on your log files for recovery. So, you must discuss this option with your DB admins to see if this is acceptable in your environment.

RESOLVED

Changed the model type of the database to Simple, and used the Shrink command to take that baby down to 500 KB.

Thanks for all of the help!