Our SharePoint 2010 WSS_Logging database is over 50GB in size and I'm now being moaned at by our DBA's. So, I ran the following Powershell script:
Set-SPUsageDefinition -Identity "Sandboxed Requests" -DaysRetained 1
Set-SPUsageDefinition -Identity "Content Import Usage" -DaysRetained 1
Set-SPUsageDefinition -Identity "Workflow" -DaysRetained 1
Set-SPUsageDefinition -Identity "Clickthrough Usage" -DaysRetained 1
Set-SPUsageDefinition -Identity "Content Export Usage" -DaysRetained 1
Set-SPUsageDefinition -Identity "Page Requests" -DaysRetained 1
Set-SPUsageDefinition -Identity "Feature Use" -DaysRetained 1
Set-SPUsageDefinition -Identity "Search Query Usage" -DaysRetained 1
Set-SPUsageDefinition -Identity "Site Inventory Usage" -DaysRetained 1
Set-SPUsageDefinition -Identity "Sandboxed Requests Monitored Data" -DaysRetained 1
Set-SPUsageDefinition -Identity "Timer Jobs" -DaysRetained 1
Set-SPUsageDefinition -Identity "Rating Usage" -DaysRetained 1
And have run the the following Timer Jobs:
Usage Data Import, and Usage Date Processing, but still, the database remains at over 50GB. I havr truncated the log (which saved me 1GB), and am now considering shrinking the .mdf (as this should reclaim 20GB). Does anyone have any suggestions (apart from recreating!)