Our Small Business Server 2008 installation has recently run out of drive space on the C drive. While working to free up space I noticed that SharePoint_Config__log.LDF is 4.4GB. The associated database is only 5MB and the main content database is only 26MB. This SharePoint installation doesn't really get used at all (unless it's used by the SBS admin site or something that's automatically installed).
I have discovered that SharePoint uses SQL Embedded Edition and I can't connect to it using SQL Management Studio. I tried various methods I discovered online.
I tried to connect in SSMS using the server name "\.\pipe\MSSQL$MICROSOFT#SSEE\sql\query" which seemed to work for some people but not for me.
I tried to use SQL Server Client Network Utility to set up an alias to the named pipe but that didn't work either. Here's where I found the instructions to connect.
Of course I tried connecting directly to \MICROSOFT#SSEE and it didn't work.
All these attempts were from SSMS running on the server where SharePoint and the database reside while logged in as an admin so it shouldn't be a remote access issue with SSMS. Just to be sure it wasn't causing the problem I used the surface area configuration tool to enable named pipe remote connections for MICROSOFT##SSEE but it didn't help.
In all cases I get an error telling me that it can't connect because the server wasn't found or wasn't accessible. The error message are slightly different for the different methods but they all say basically the same thing.
Please help me out. In a single day I've gone from SharePoint-agnostic to SharePoint-annoyed and I'm heading toward anti-SharePoint. Option B for me is to remove SharePoint entirely but I don't know if any of the SBS features depend on it. At the moment we don't use it for anything at all.
If I can get SSMS to connect to the database I'm comfortable that I can deal with the log file but I just can't connect.
In addition to fixing the problem in the near term I would like to know how to stop it from happening again. Why would the config log file balloon up like that when SharePoint isn't even getting used?
Update: Suddenly I no longer got the error from SSMS about the server not existing I started getting a login error when using "\.\pipe\MSSQL$MICROSOFT#SSEE\sql\query". I can only assume it's because I deleted a bunch of IIS log files to free up space. After that I had to close SSMS and specifically open it using Run as Administrator and then I was able to connect to the SharePoint database. After that I was able to backup the log file and shrink it (with a minor change detailed in my comment on the accepted answer).