Invision Community 4: SEO, prepare for v5 and dormant account notifications By Matt Monday at 02:04 PM
Connor Hawke Posted May 31, 2016 Posted May 31, 2016 I don't know why but ever since IPB 4, the database file is more than twice the size it was on IPB 3 with basically the same amount of content - at least half a gigabyte now. Are there any tables in the database that can be safely cleared? I can keep a backup of the full original contents in case I need to reimport something, but since I may do regular backups while developing my site it is not ideal to have subsequent backups be so space-consuming.
AndyF Posted May 31, 2016 Posted May 31, 2016 Have a look at the database in phpmyadmin or similar tool. Do you have two sets of all tables ? I'm only thinking if it ran the utf8 conversion it may of likely saved the original ones typically with an orig_ prefix. See here too: https://invisionpower.com/forums/topic/428743-did-upgrade-database-went-from-3gb-to-18gb/
Connor Hawke Posted June 1, 2016 Author Posted June 1, 2016 14 hours ago, AndyF said: Have a look at the database in phpmyadmin or similar tool. Do you have two sets of all tables ? I'm only thinking if it ran the utf8 conversion it may of likely saved the original ones typically with an orig_ prefix. See here too: https://invisionpower.com/forums/topic/428743-did-upgrade-database-went-from-3gb-to-18gb/ Yeah I did the utf8 conversion and there are orig_ tables there. Is it safe to drop or clear those?
Nathan Explosion Posted June 1, 2016 Posted June 1, 2016 2 hours ago, Connor Hawke said: Yeah I did the utf8 conversion and there are orig_ tables there. Is it safe to drop or clear those? It is safe BUT it depends on whether you did the "switch the prefix to test then switch it back if you are happy" portion of the conversion. To be 100% safe - check your conf_global.php file and confirm what your active prefix currently is. If it isn't orig then you can go ahead and drop the orig tables.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.