|
Pedro Ordenes
|
June 17, 2019 at 12:15 pm
Hello,
My name is Moses Kaplan, I am contacting you on behalf of my employer Water World Swim. Please cc all responses to the email: mosesakk@gmail.com as I will be the person responsible for this correspondence/issue.
WWS uses SiteGround as its web hosting provider, and has used EE for a long time to register participants in all of its events. Just last week we received a notice from SiteGround that our SQL database is exceeding its size capacity. Upon investigation I have identified the following 2 tables are taking up massive amounts of storage space:
wp_esp_line_item
wp_esp_message
I am quite sure that the upper table (line_item) is the container for all of our EE information, and am guessing the lower (message) is as well. It is imperative that we reduce our data size on our SQL database, because SiteGround will do it for us if we don’t manage it ourselves, and I’m not sure what sort of repercussions that will have.
If I were to empty the (line_item) table, what would be lost? Is there a way to backup the information without loosing it? I assume that the table is storing all transactions every encountered – which is really not important for us. Is there a way to archive anything that is over 1 year old and just export that data as a report and then remove it from the server? Can any/all of this be done from the backend of Event Espresso/this site?
We want to continue using EE as it is very integrated into our current business model, but I need to understand how to reduce the table size. Please advise the best course of action. Please be sure to cc all correspondences to: mosesakk@gmail.com
Thank you very much and I will look for your speedy reply.
Cheers,
Moses Kaplan
Water World Swim
mosesakk@gmail.com
|
|
Josh
|
June 17, 2019 at 12:28 pm
Hi,
With regards to the wp_esp_message table, you can empty that table. Then, you can go to Event Espresso > Messages > Settings and set the “Cleanup of old messages:” to 3 months. This will activate a cleanup schedule that will remove any entries older than 3 months, going forward.
With regards to _esp_line_item, I would not advise to empty that table. What you could do instead is delete the oldest of those entries, leaving the newer entries to remain. This will result in orphaned transaction data, but if you do not look up older transactions it shouldn’t be a problem.
|
|
Pedro Ordenes
|
June 17, 2019 at 12:34 pm
Hi Josh,
Thanks so much for the reply. I have emptied the _message table and updated the settings on the Messages for EE in the backend of the wp site!
For the line_item table is there a way to export that data before deleting it from phpMyAdmin? For archiving? I don’t believe WWS needs to have data over 12 months staying in the server, but I don’t think it’s a good idea to just completely trash it – if that is all the transaction history…
How would you recommend to get an archive of the transaction data?
Thanks again so much for your response.
|
|
Josh
|
June 17, 2019 at 12:39 pm
Yes, PHPmyAdmin has an export feature. You can use that to select the table, then back it up to a hard drive or something. You could even make a backup of the entire site’s database and import it onto a locally hosted site, which would allow for archival access.
|
