Reducing Database Size for MailPoet Tables
It is common for customers to contact us with inquiries about the size of the MailPoet database. Database usage will be highly dependent on your plugin's usage and will grow as your list grows over time. If your setup requires the use of many Welcome Emails (e.g. to emulate a Drip campaign) or automatic emails (Post Notifications and WooCommerce emails), the size of the table may indeed grow faster.
You can read more about MailPoet tables and how they may affect your website's performance on the Performance FAQ page.
Normally neither the size of the table nor the number of tables should be an issue, unless you're experiencing performance issues caused by our plugin or your hosting company enforces a relatively low DB size limit.
In this case, you should either request your hosting provider for an increase or delete some of the old emails and data from the plugin.
If you're an experienced user and are comfortable with accessing your database and you want to decrease the size of a specific MailPoet table(s) in your database, you can use some SQL queries to remove data older than a specific date (e.g. anything older than 2019-01-01) and free up some space. You should search for the prefix *_mailpoet to identify the MailPoet tables.
You may want to take a look at these tables:
- _mailpoet_sending_queues
- _mailpoet_scheduled_tasks
- _mailpoet_statistics_newsletters
- _mailpoet_newsletter_links
- _mailpoet_scheduled_task_subscribers
- _mailpoet_statistics_clicks
- _mailpoet_statistics_newsletters
- _mailpoet_statistics_opens
If you're not comfortable with performing these changes in the database, you can start by deleting old data in the plugin, e.g.: old newsletters sent, inactive automated emails, and unconfirmed subscribers.