Our sharepoint server 2010 WSS_Logging database is about 100GB and counting ... (Farm DB ~1TB / ~100 000 pages viewed per day / ~5000 unique users per days)

I've reduced

  • retention and logging levels for all services (through the central sharepoint admin for logging files) to 6 days
  • Logging/Usage consolidation to 6 days (through powershell)

I assume this is usage data collection which take the more place, but these data are also used for Web Analytics

Is there any scenario for "large" sharepoint farm & usage data management ? I can't find reference/white paper on this topic.


These guidance posts may be helpful as scenarios can vary -

UPDATE: Usage logging databases require ongoing maintenance. You can plan on how it's going to be used by selecting the tracing variables and other parameters and also by periodic clean-up tasks (archiving) using PowerShell or other utilities. There's a Sharepoint 2010 Capacity Planning and Sizing Tool that can be helpful in gauging your deployment.

|improve this answer|||||
  • I've already followed most of the advices regarding the WSS_Logging database which I can find in your link. The extra advice is to relocate the WSS_Logging but it has a cost (our SQL servers are managed by external provider). Moreover this solution do not fix the primary problem which is database size, and not overall farm performance. – camous Mar 23 '12 at 14:05
  • I posted an update to my response above. – Supriyo SB Chatterjee Mar 23 '12 at 14:47

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.