Feb 11
What to Do When the SharePoint_Config Database Log Gets Out of Control
Well, I arrived at a client this morning to perform some database maintenance on the SharePoint farm. They had previously encountered disk space issues and I was to setup a maintenance plan, along with re-arranging the location of MDF and LDF files to different volumes, as per performance best practices for databases.
To my surprise, I walked into a situation where the SQL server had suddenly run out of disk space!
Not my preferred method for starting my mornings:
The culprit was quickly identified:
First, we tried to shrink files to release unused space.
To do this, simply select the database in question, right-click and select Tasks…Shrink…Files.
Make sure you choose “Release unused space” and click OK.
This did not net much of a change.
Next, we tried a combination of SQL queries.
(First, make sure you back up your configuration database log)
Step 1:
BACKUP LOG [Sharepoint_Config] WITH TRUNCATE_ONLY
USE [SharePoint_Config]
GO
Step 2:
DBCC SHRINKFILE (N’SharePoint_Config_log’ , 50)
GO
And…voila!
