The SpectrOM DB Cleanup tool will remove selected old and unused data in your database tables and then rebuild the MySQL indexes for all of your tables. This helps to ensure that your index files do not get corrupted and that your data can be accessed efficiently.
Support Details: We are happy to provide support and help troubleshoot issues. Users should know however, that we check the WordPress.org support forums once a week on Fridays from 10am to 12pm PST (UTC -8). Daily support and issue reports are handled via our GitHub repository here: https://github.com/spectrom/spectrom-db-cleanup/issues. Please read our support notes here before creating new issues.
The SpectrOM DB Cleanup tool was specifically designed for data-driven sites such as eCommerce, Learning Management Systems and BuddyPress.
The SpectrOM DB Cleanup Features:
- Removal of selected old and unused data in your database tables
- Rebuilds the MySQL indexes for all of your tables
- Configurable so you can indicate what sections to Cleanup
- eMail a report to indicated recipients
- Automation at specified day and time
This DB Cleanup helps to ensure that your database index files do not get corrupted and that your data can be accessed efficiently.
Installation instructions: To install, do the following:
- From the dashboard of your site, navigate to Plugins –> Add New.
- Select the “Upload Plugin” button.
- Click on the “Choose File” button to upload your file.
- When the Open dialog appears select the spectrom-db-cleanup.zip file from your desktop.
- Follow the on-screen instructions and wait until the upload is complete.
- When finished, activate the plugin via the prompt. A confirmation message will be displayed.
or, you can upload the files directly to your server.
- Upload all of the files in
Once activated, you can configure the plugin via the Settings -> SpectrOM DB Cleanup menu.
- How often should I have the Cleanup operation scheduled.
This depends on the size of your site and how often things are being updated. If you are posting new content all the time or have several users making comments, you might want to run the Cleanup every other day. If you have an eCommerce site with several purchases made every day, running the Cleanup every day will keep the session table from becoming corrupted and ensure that users can continue using the shopping cart.
Some recommended settings:
- Sites with 0-5,000 visitors per day should schedule the Cleanup for every seven days.
- Sites with 5,000-10,000 visitors per day should schedule the Cleanup for every five days.
- Sites with 10,000-30,000 visitors per day should schedule the Cleanup for every other day.
- Sites with over 30,000 visitors per days should schedule the Cleanup for every day.
- What time of day should I schedule the Cleanup?
It’s best to run the SpectrOM DB Cleanup at a time when your site has few visitors. The Cleanup can take anywhere from five seconds to as much as a minute or two, depending on the size of the database. Users can view the site during this time, but they might notice some slowness.
To find what time of day has the lowest traffic on your site, you can use Google Analytics. To do this, click on “Customization” in the top bar of your Analytics Dashboard then choose “Custom Report.”
This brings you to the report builder table. Here you can build a basic visitors and eCommerce report so you can view visitor behavior based on day of week and hour of day.
Give your report a name and set up two Metric Groups: one for Visitors and another for eCommerce.
You can add any metrics you like here by just clicking on “+ add metric” and searching for the data you need. Once you have the metrics labeled and selected, you need to choose the “Dimensions.” This is where you set day and time.
Let this report run for a couple of weeks to gather data on your user’s behavior. Then you can adjust the time that the SpectrOM DB Cleanup is run accordingly.
- Fix typo in plugin description.
- Tested with WordPress 4.4.
- Some code cleanup and minor optimizations.
- Fix bug with credentials check – thanks to @jb510 for pointing that out.