Is there an easy way to keep the database size down (or reduce the size) in Umbraco v4? I have a smallish site (<100 pages) and the database is 2.9GB. I've recently switched off logging and cleared out the umbracoLog table, but I notice that the cmsPropertyData table still has 6.6 million rows which seems quite large to me? I've seen people posting scripts to clean out previous versions of data, is that my only option?
Thanks Doug, that makes sense - the Umbraco app was originally created by another company and I completely forgot that there is a scheduled publish event that imports news articles from a web service. I'll have more of look at the import process, and look at those scripts to clear out the excess data rows.
Large database - keeping the size down
Is there an easy way to keep the database size down (or reduce the size) in Umbraco v4? I have a smallish site (<100 pages) and the database is 2.9GB. I've recently switched off logging and cleared out the umbracoLog table, but I notice that the cmsPropertyData table still has 6.6 million rows which seems quite large to me? I've seen people posting scripts to clean out previous versions of data, is that my only option?
There are two things to do.
1. Backup the database and then clean out previous versions according to the instructions you'll find on the web. I did mention backups, right? :)
2. Find and resolve the source of the problem. I would guess there is a scheduled publish event that is causing the issue.
This old forum thread for umbraco v3 will be good background reading: http://forum.umbraco.org/yaf_postst6564_305-Database-Huge--cmsPropertyData--392MB.aspx
You'll also find Thomas' blog helpful. Especially http://blog.thoehler.com/2009/02/27/cleaning-all-unnecessary-versions-via-sql as well as Hendy's at http://blog.hendyracher.co.uk/umbraco-database-part-1/
cheers,
doug.
Thanks Doug, that makes sense - the Umbraco app was originally created by another company and I completely forgot that there is a scheduled publish event that imports news articles from a web service. I'll have more of look at the import process, and look at those scripts to clear out the excess data rows.
Something that might also help is setting the Recovery model to simple
is working on a reply...