Reduce Sharepoint services 3.0 log.ldf files…

I had the problem that Sharepoint_Config-ID-.log.ldf grow realy BIG (14GB) on a content database of 1 GB!

You can solve this problem by using “Shrink” command in the MS SQL Server Management Studio Express

First you need to connect to your Sharepoint 3.0 database called: \.pipemssql$microsoft##sseesqlquery – just put this string in your “Server name” field:

\.pipemssql$microsoft##sseesqlquery

 Create full backup of all databases before continuing!

After that we should change restore mode from “Full” (this the parameter that allows .log.ldf to grow that large as transaction logs are not purged) to “Simple”:

Expand Databases, right mouse click on Sharepoint_Config… Properties, Options, Recovery model: Simple and click OK

Shrink the database procedure:

Expand Databases, right mouse click on Sharepoint_Config… Tasks, Shrink, Files in File type select Log and click OK
Your log file will become radicaly smaller. 🙂

Be sure you backup your databases before this procedure and also on daily bases…

Good luck!

 Also check:
http://geekswithblogs.net/RogueCoder/archive/2008/06/03/122588.aspx
http://www.karaszi.com/SQLServer/info_dont_shrink.asp

27 thoughts on “Reduce Sharepoint services 3.0 log.ldf files…

  1. Fabian Tuender

    Great, this was the information I was looking for. I knew how to shrink the database but has problems accessing the server. Thanx to your servername string I was able to connect. Thanx!

    Like

    Reply
  2. mohit

    Thank you! you explained it in very simple words. It worked for me and saved us from potential downtime and few sleepless nights. — Regards

    Like

    Reply
  3. Rodney

    Thanks Luke! you saved me 8Gig in 30 seconds and good timing as my drive was sitting at 200mb free space 🙂

    Also a mention to Google for finding the page for me…

    Awesome.

    Like

    Reply
  4. Christian H.

    Sounds like a nice solution, but what if I get “Login Failed” – I am logged in to Windows with the only Windows Admin account. This is the standard SBS 2008 installation, can’t think of ever having set any Admin passwords for the WSS database.

    Like

    Reply
  5. CIU

    Excellent solution! We had our logs on SharePoint_Config getting up to 17gigs and our WSS_Content up to 35gigs. Ran the shrink file on both databases and now logs nearly at 0. Also thanks for the correct database string path.

    Like

    Reply
  6. Jsmith

    This worked on the ShareWebDB database but when i tried to go to the properties of the Sharepoint_Config database i get and SQL error that says:
    Property Owner is not available for Database ‘[SharePoint_Config_29c26fca-17b8-48c1-9704-b869932abcb6]’. This property may not exist for this object, or may not be retrievable due to insufficient access rights. (Microsoft.SqlServer.Express.Smo)

    This appears to be the same error on other of servers.

    Like

    Reply
  7. Alan

    How do you “connect” to the SharePoint database? When I open SQL studio, the only db listed is my Antivirus one, and when I do File-> Connect, the only db’s I can browse to are other SQL instances installed by 3rd party apps, or SBS Monitoring: the SharePoint DB is not listed. Help! this is so frustrating! My C drive is almost out of pace due to 20GB ldf file, and I’ll need to forcefully remove SharePoint completely if I can’t get rid of the stupid ldf file.

    Like

    Reply
  8. Grant

    Thanks a lot for the \.pipemssql$microsoft##sseesqlquery information! None of the other dozen or so articles I found mentioned this, and I had no idea how to access the database.

    Like

    Reply

Leave a Reply

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

WordPress.com Logo

You are commenting using your WordPress.com 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 )

Google+ photo

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

Connecting to %s