- Your SQL instance may create excessive logs about a login failure. The solution: make a domain service account with access to "BUILTIN\Windows Authorization Access Group" (also recommended to make said user a "guest" and not a "user").
- Your SQL logs may get too big for practical use. The solution: change the number of log files, and have a SQL agent run EXEC sp_cycle_errorlog on the databases.
- Regular log files will eat up a lot of space. Use WinDirStat to identify where you have said files, and compress those folders via folder properties (ex: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS). Remember not to compress the MSSQL program folders or databases.
- Your LDF files for SQL may get huge from Sharepoint event logging. In Sharepoint Powershell, run Set-SPUsageDefinition -Identity "Page Requests" -DaysRetained 3 and then use the Sharepoint Management Studio to run "Usage and health data collection" (I set the disabled job to run overnight, and told it and the other default job to run manually for catchup).
Friday, September 13, 2013
Sharepoint drive space issues
Over the past two months, I have been taming a Sharepoint 2010 instance to use less disk space (among other issues).