- Windows SharePoint Services (WSS)) 3.0 uses the Windows Internal Database. It installs on a Windows machine as SQL Server (folder name) but doesn't appear in Add/ Remove programs.
- The Windows Internal Database can be accessed using Microsoft SQL Server Management Studio Express 2005. Download it here.
- It's usually not the database that grows too large (WSS_Content.mdf or any .mdf) it's usually one of the log files (like SharePoint_AdminContent_xxxxxx_log.ldf). Mine grew to 7GB.
- In order to fix this problem we want to shrink or truncate the SQL Server Transaction Log and we can do it without using any separate queries or commands like
In order to shrink the SharePoint Services database (aka Windows Internal Database) log file we need to do a few things. Here are the steps that worked for me:
- Install SQL Server Management Studio Express 2005 on the machine with SharePoint Services 3.0.
- Open Management Studio
- Connect to the Windows Internal Database by using this as your server name:
- Windows Authentication is fine. Click connect.
- Expand the Databases tree and you should see several SharePoint and WSS_Content databases.
- It's recommended you backup all your databases before continuing on. For more information go here.
- Right click on the database you want to shrink the log file of and go to Properties > Options.
- Change the recovery mode to Simple and Click OK to apply the changes. (This is the only way SQL Server will be able to dramatically shrink the SQL Server Log files)
- Right click on the database again and go to Tasks > Shrink > Files
- For file type select Log and click OK to begin shrinking the log file.
- Repeat this step for whatever log files you need to shrink.
- To compact the actual database instead of the log files, keep the file type (step #10) to data.
- Be sure to reset the Recovery Mode back to Full when you're done.
That's all there is too it. You've now accessed the Windows Internal Database for Windows SharePoint Services 3.0 and shrunk both the databases and log files. I performed this task on my Windows Home Server which was running out of room thanks to a few log files that totaled 8GB.