Database maintenance should solve an observed problem, not become a ritual of running “optimisation” tools. The safest approach is to measure growth, identify the tables and feature responsible, back up the database, and change only data that has a documented owner and retention decision.
Know what the database contains
The WordPress database usually stores content, settings, users, comments and metadata. Plugins can add order records, form submissions, logs, scheduled actions, sessions and custom tables. Deleting a plugin does not always remove its data, and a generic cleanup tool cannot reliably understand every business record.
Measure before cleaning
| Signal | What it may indicate |
|---|---|
| Rapid table growth | Logs, sessions, analytics, scheduled actions or failed jobs |
| Large options/autoload data | Plugins loading excessive configuration on every request |
| Many revisions or transients | Normal history, stale cache data or poor retention settings |
| Slow administrative screens | Heavy queries, external calls, hosting pressure or database design issues |
| Failed scheduled actions | Extension or payment jobs repeatedly retrying |
| Unknown tables | Old plugins, custom development or incomplete migration |
Back up and define retention
Create and verify a database backup before deletion, repair or search-and-replace work. Decide how long orders, enquiries, logs, revisions and personal data should be retained. Legal, accounting and operational obligations can differ, so do not use a “delete everything older than 30 days” rule without understanding the records.
Prefer the owning application
Use WooCommerce, the form plugin or another owning system to manage its records when it provides supported tools. The application understands relationships that a generic database cleaner may not. Use direct SQL only when a competent operator understands the schema, has a tested query and can restore the database.
Handle revisions, transients and logs carefully
- Revisions provide recoverability and editorial history; limit them only when storage or workflow justifies it.
- Transients are temporary data, but plugins can use them differently; investigate repeated growth rather than repeatedly purging symptoms.
- Logs should have a retention policy and must not expose credentials or customer data.
- Expired sessions and abandoned jobs can be removed through supported product tools after their effect is understood.
Do not confuse export with recovery
An SQL export can protect the database but not uploads, code or server configuration. A complete recovery plan combines database and files from a compatible point in time. Keep the exact table prefix and environment details with the recovery notes.
Verify after maintenance
- Load public pages and search.
- Log in with relevant roles.
- Create and edit content.
- Submit forms or a test order.
- Run scheduled actions and check queues.
- Compare table size and performance with the baseline.
- Confirm no expected records disappeared.
When specialist help is justified
Obtain technical help before deleting unknown tables, repairing repeated corruption, changing character sets, editing serialized values or cleaning a live commerce database. These tasks can appear successful while silently disconnecting relationships between records.
A useful specialist report should identify the affected tables, measured problem, proposed query or tool, backup point, estimated impact, acceptance checks and rollback method. “Optimise the database” alone is not an adequate scope.
Practical next step
Open the hosting database report or a trusted diagnostic view, identify the five largest tables and determine which feature owns each one before installing any cleanup plugin.
Sources and date checked
This guide was checked on 21 July 2026. WordPress, plugins, hosting platforms and commercial terms change, so confirm the current documentation and licence details before making a material change.
Keep the decision under your control
Retain the relevant accounts, source material, supplier terms and recovery information. Recheck changing prices, interfaces and rules before acting.