Strategies for reducing database size
Several weeks ago, we experienced a server outage due to a lack of storage space on the database server. And we have received some reports from IT that the DB server continues to be close to full.
Could we talk about ideas for reducing database size? A few initial ideas:
1. In my experience, it's often the case that a small number of sites are responsible for a disproportionate amount of DB storage space. We could develop a tool that analyzes existing sites and identifies these sites, and then work to discover what's causing the disproportionate use. We could then, on a case-by-case basis, take mitigating steps: decommissioning sites, culling excess or inappropriate data, fixing bugs that might cause inappropriate database use, moving blob assets out of the DB and into the filesystem, etc.
2. Explore a strategy for deleting/decommissioning/archiving empty sites. It's likely that a large number of sites have been created but never used, and can be safely removed.
3. Explore a strategy for archiving legacy sites. This might involve rendering them as HTML and saving them to the filesystem, then deleting them from the WP installation. This is the strategy most likely to have a long-term impact on storage space, but is also the strategy that will involve the most technical and outreach work.
Other ideas or thoughts?