Comments on: Reduce Sharepoint services 3.0 log.ldf files…

By: Grant

Grant — Tue, 11 Dec 2012 21:26:29 +0000

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

By: Dave

Dave — Thu, 01 Nov 2012 15:43:03 +0000

By far the best thing to happen to my job! You just freed up over 20GB with just this. Thank you, thank you, thank you!

By: Alan

Alan — Fri, 13 Apr 2012 08:57:07 +0000

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.

By: Leif Stenfeldt

Leif Stenfeldt — Wed, 21 Mar 2012 09:41:33 +0000

You are my hero – thanks for sharing your knowledge.

By: Steven

Steven — Mon, 09 Jan 2012 07:04:29 +0000

Brilliant. Thanks!

By: Mike

Mike — Mon, 17 Oct 2011 19:20:58 +0000

Thanks! This really helped, I was down to 2GB of disk space.

By: dotNetFollower

dotNetFollower — Sat, 06 Aug 2011 01:47:57 +0000

Hello! Here is the almost same way to shrink sharepoint database transaction log. Thanks!

By: jsmith

jsmith — Fri, 27 May 2011 03:55:37 +0000

Same error running as administrator logged into server as administrator

By: manojlovicl

manojlovicl — Thu, 26 May 2011 22:54:04 +0000

You shuld run SQL management as administrator / right click / run as administrator

By: Jsmith

Jsmith — Thu, 26 May 2011 17:47:40 +0000

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.