The sessions table should be automatically purged each time someones logs in.

I think the "history" table may be the problem. You can deactivate history in the configuration.

mistic100 wrote:

hi,
I'm pretty sure the responsible of the huge database is the table "piwigo_session", if you are very limited in space you can truncate it (and not delete) through PHPMyAdmin (note it will be filled again with time)

you can use multiple database but it's a bit tricky,
-first of all, all your databases must be accessible with the same user/password and on the same host (ex: localhost)
-then create your databases and move the tables you want into them
-finally add and modify the needed lines among this in you local config file (local/config/config.inc.php)

Code:

define('CATEGORIES_TABLE', $prefixeTable.'categories');
  define('COMMENTS_TABLE', $prefixeTable.'comments');
  define('CONFIG_TABLE', $prefixeTable.'config');
  define('FAVORITES_TABLE', $prefixeTable.'favorites');
  define('GROUP_ACCESS_TABLE', $prefixeTable.'group_access');
  define('GROUPS_TABLE', $prefixeTable.'groups');
  define('HISTORY_TABLE', $prefixeTable.'history');
  define('HISTORY_SUMMARY_TABLE', $prefixeTable.'history_summary');
  define('IMAGE_CATEGORY_TABLE', $prefixeTable.'image_category');
  define('IMAGES_TABLE', $prefixeTable.'images');
  define('SESSIONS_TABLE', $prefixeTable.'sessions');
  define('SITES_TABLE', $prefixeTable.'sites');
  define('USER_ACCESS_TABLE', $prefixeTable.'user_access');
  define('USER_GROUP_TABLE', $prefixeTable.'user_group');
  define('USER_INFOS_TABLE', $prefixeTable.'user_infos');
  define('USER_FEED_TABLE', $prefixeTable.'user_feed');
  define('RATE_TABLE', $prefixeTable.'rate');
  define('USER_CACHE_TABLE', $prefixeTable.'user_cache');
  define('USER_CACHE_CATEGORIES_TABLE', $prefixeTable.'user_cache_categories');
  define('CADDIE_TABLE', $prefixeTable.'caddie');
  define('UPGRADE_TABLE', $prefixeTable.'upgrade');
  define('SEARCH_TABLE', $prefixeTable.'search');
  define('USER_MAIL_NOTIFICATION_TABLE', $prefixeTable.'user_mail_notification');
  define('TAGS_TABLE', $prefixeTable.'tags');
  define('IMAGE_TAG_TABLE', $prefixeTable.'image_tag');
  define('PLUGINS_TABLE', $prefixeTable.'plugins');
  define('OLD_PERMALINKS_TABLE', $prefixeTable.'old_permalinks');
  define('THEMES_TABLE', $prefixeTable.'themes');
  define('LANGUAGES_TABLE', $prefixeTable.'languages');

PS : don't forget to backup your files and your original database

Thanks for your quick reply and help. At least now I have  more database space to deal with so hopefully I won't have to deal with multiple databases. I will print this out for future reference.

NWS wrote:

[...] I see a section named "portfoliohistory". It has over 178,000 entries. Would this be the area you're referring to?

Yes, and 178k lines is not that big (I have a "history" table with over 10M lines)

I also see an "empty" button. Can I use that safely or will that corrupt the database?

Use the purge actions in Piwigo instead [Administration > Tools > Maintenance]

You mention deactivate history in the configuration. Is that somewhere in Piwigo?

[Administration > Configuration > Options > History]