Thanks, I'll read up on them. 900MBs of database for a simple blog is insane. The size is not really a problem in terms of storage space, but it is causing me headaches in terms of backup. Takes too long to backup a copy of the database.
If I can't considerably reduce the db size I fear I'll migrate the site to another solution :(
can you tell us which of the tables causes such a large size of the dump? If it is ezsession then you should run clean up scripts like my previous writers told you - if it is ezcontentobject_attribute you may check the number of versions you store and the number of attributes in this classes.
I cleaned up the sessions, and wow. I mean, WOW! Incredible:
-rw-r--r-- 1 christian users 904M 2009-07-18 21:58 20090718-1.sql
-rw-r--r-- 1 christian users 25M 2009-07-18 22:02 20090718-2.sql
That's pre and post session cleanup. Problem solved :) Thanks alot all!
Kracker: I'd be interested to know how you recon storing comments in the content tree is a problem? In what other way can I really store them? If you're thinking about the tree menu, I obviously don't show them there. I have quite a bit of content, and haven't had any real performance trouble yet...
I asked Heath to add a node about this topic on eZpedia, <i>http://ezpedia.org/en/ez/solution_how_to_shrink_or_reduce_the_site_of_ez_publish_database_backup_dump_files</i>
