SharePoint Config Log bloating

The SharePoint Config Log file has a tendency to grow very large.

In order to reduce it we have to run the shrink task included in the Microsoft SQL Server Management Studio.

If you haven’t installed the Microsoft SQL Server Management Studio 2005 or 2008. Download it from the Microsoft website.

Start Microsoft SQL Server Management Studio

On the Connect to Server Windows use the following Server Name: \\.\pipe\mssql$microsoft##ssee\sql\query

Locate WSS_Content database and right-click

Select Tasks and select Shrink then Files

From the Shrink File Windows select Log from the drop-down

Click ok and this should resolve this problem!

About apoth0r
IT Professional and Cloud Evangelist! & Streamer! Managed Services | Solutions | Procurement | Support Services | Cloud | Fujitsu

4 Responses to SharePoint Config Log bloating

  1. Wondering if you could let me know something. What does shrinking the log file for WSS_Content have to do with in relation to shrinking the SharePoint Config log file? Are you saying that shrinking the WSS_Content log will fix why the Config log bloats so insanely?


  2. Hi Marty,

    This isn’t a fix for the bloating as such, it is a way of reducing the size of the file after it has bloated. Unfortunately I am by no means a SQL expert but having managed the drive space for a particular customer, I came across this fix and thought I’d share.
    I unfortunately do not know the reason for this bloating other than something is erroring at a rapid rate or in fact a condition of the ‘SBS’ underbelly.

    Sorry I’m not as conclusive as you’d like


    • martynelsonjr says:

      Thanks for the speedy reply Steve. I’m on the same page in terms of knowing how to utilize the shrink file task. Your article started out by mentioning the config log file bloating. So I mostly was wondering why you were finding it beneficial to shrinking the WSS_Content log instead of attacking the Config log directly.

      Thanks again.

      • I’m afraid I don’t have an answer to that other than, when I ran this fix, it worked for this particular customer. Unsure of whether it being an SBS server would have any effect on the entire ‘backend’ of the logs as you well know SharePoint is a ‘module’ of SBS 2008 and I presume that this in some way caused a generic bloat (although the SharePoint config file was bloated) this worked for me and resolved the issue.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: