2) for each table, run the SQL statement: ALTER TABLE wt_xxx ENGINE=InnoDB;
I had time tonite to play with the MySQL database to see which size reduction mechanism would work for me. Starting with an MYSQL database that was 158MB, I have been able to reduce the MySQL database size to 46MB. My maximum size limit on the server was supposed to be 128MB, thank goodness something is/was misconfigured or flexible on their server. Perhaps there is a built-in safety factor that saved me :)
For whatever reasons, trying the two methods Greg mentioned (and I would have preferred to use), I could not produce any affect on the size of the database using either the tools in cpanel or PhpMyAdmin. The server is probably not configured properly for method #2 even though getting a green check mark in PhpMyAdmin when executed on each table. Trying method #1 two different ways failed to reduce the database size
I ended up exporting the GEDCOM file from webtrees and then importing that GEDCOM into a fresh MySQL database. As mentioned by forum member Warius I did lose login and account credentials for all (7) members, plus all webtrees settings that I had changed, and HTML Blocks info, FAQ, Email settings, page block changes, etc. so it is important to back up that information to reset the webtrees to how you had it to keep what you have changed. If you choose this method then take the time to copy the settings, you will be glad you did! If you are as I am there will be a lot of different settings to copy.
Individual media permissions for documents. photo's, etc. are retained in the GEDCOM. System-wide media permissions are not.
All in all everything went smoothly, what took longest was resetting all the changes I had copied.