Title: Shabnam Tornado Database Maintenance
Author: SHABNAM
Published: August 14, 2026
Last modified: August 14, 2026
---
Search plugins
# Shabnam Tornado Database Maintenance
By [SHABNAM](https://profiles.wordpress.org/shcd/)
[Download](https://downloads.wordpress.org/plugin/shcd-database-maintenance.1.0.0.zip)
* [Details](https://az-tr.wordpress.org/plugins/shcd-database-maintenance/#description)
* [Reviews](https://az-tr.wordpress.org/plugins/shcd-database-maintenance/#reviews)
* [Installation](https://az-tr.wordpress.org/plugins/shcd-database-maintenance/#installation)
* [Development](https://az-tr.wordpress.org/plugins/shcd-database-maintenance/#developers)
[Support](https://wordpress.org/support/plugin/shcd-database-maintenance/)
## Description
Shabnam Tornado Database Maintenance is a database inspection and maintenance toolkit
for WordPress administrators and developers. It combines preview-first cleanup,
integrity checks, verified logical backups, reference discovery, and an optional
controlled Post ID reindex workflow.
The plugin reads the active WordPress table names from `$wpdb`. It does not assume
the default `wp_` prefix, so installations using custom prefixes such as `shcd_`
are supported.
Post ID reindexing is an advanced, destructive operation. It is disabled by default,
is not required for ordinary cleanup, and should be tested on a staging copy before
use on a production site.
#### Main features
* Database schema discovery through `INFORMATION_SCHEMA`, including tables, columns,
indexes, engines, and foreign keys.
* Preview-first cleanup for revisions, auto drafts, trash, autosaves, pending revisions,
expired transients, and supported orphaned records.
* Configurable WordPress revision retention and an optional independent revision
archive.
* Logical SQL backups with file checksums, database fingerprints, and consistency
reporting.
* Integrity checks for WordPress core relationships and supported plugin data.
* Dry-run reports before destructive maintenance.
* Controlled `AUTO_INCREMENT` normalization without renumbering existing rows.
* Reversible quarantine for suspected unused plugin tables before permanent deletion.
* Audit logs, operation reports, retention controls, and WP-CLI commands.
* Optional repair and cache rebuilding for Elementor-related data after a completed
reindex.
#### Controlled Post ID reindexing
The optional reindex workflow creates a dense `1..N` sequence for rows in the active`
$wpdb->posts` table. This includes posts, pages, custom post types, revisions, and
Media Library attachments that still exist when the mapping is created.
Tornado uses a collision-resistant two-phase mapping:
1. Build an immutable Old ID to Temporary ID to Final ID mapping from the current
Posts table.
2. Move registered references from Old IDs to Temporary IDs.
3. Move the Posts primary keys from Old IDs to Temporary IDs.
4. Move registered references from Temporary IDs to Final IDs.
5. Move the Posts primary keys from Temporary IDs to Final IDs.
6. Verify reference parity, row counts, sequence boundaries, zero gaps, and the final`
AUTO_INCREMENT` value.
The Posts table is the source of truth for the mapping. Adapters synchronize references;
they do not independently choose or renumber the Posts primary-key sequence.
Reindex execution requires matching Discovery, Mapping, and Backup fingerprints.
It also requires supported transactional tables, successful Preflight checks, administrator
capabilities, a REST nonce, a session-bound one-time authorization token, and an
explicit confirmation phrase. Blocking failures before commit cause the operation
to stop or roll back.
#### Adaptive plugin-reference detection
Tornado includes dedicated reference handling for known relationships and a conservative
adaptive detector for conventional plugin tables.
The adaptive detector can evaluate:
* Integer columns with semantic names such as `post_id`, `page_id`, `product_id`,
or `attachment_id`.
* Polymorphic pairs such as `object_id` with `object_type`, or `element_id` with`
element_type`.
* Strictly formatted ID lists in semantically named columns.
* Supported JSON and PHP-serialized paths that clearly represent WordPress object
IDs.
* Explicit foreign keys that reference the active Posts table.
Detection is evidence-based. The plugin checks column type, naming, mapping intersection,
row resolution, table scope, and compatible WordPress post types. Ambiguous, encrypted,
compressed, binary, proprietary, remotely stored, or free-text references are not
guessed. They remain blocking until an administrator selects an explicit policy
or a dedicated adapter is provided.
#### Plugin and builder compatibility
Tornado includes dedicated or structured handling for selected WordPress, WooCommerce,
Elementor, Gutenberg, and Rank Math relationships. It also exposes an adapter registration
hook for site-specific integrations.
Compatibility does not mean that every extension or external system can be detected
automatically. IDs copied to a CRM, ERP, payment gateway, search service, mobile
application, custom API, arbitrary HTML, shortcode, URL, or remote database may
remain outside WordPress and must be reviewed separately.
#### Cleanup and revision management
Cleanup operations provide a Preview before deletion and operate in bounded batches.
Supported cleanup categories include:
* All revisions or only revisions beyond the configured retention limit.
* Auto drafts, trash, autosaves, and optionally aged pending revisions.
* Orphaned post meta, comments, comment meta, user meta, term meta, and term relationships.
* Selected WooCommerce orphaned lookup and permission data.
* Expired transients.
* Stale local media rows covered by the plugin’s explicit media policies.
The optional revision archive stores selected snapshots in Tornado’s own table instead
of keeping ordinary WordPress revision rows indefinitely. Elementor and WooCommerce
content can be included according to the configured archive policy. This archive
does not replace Elementor’s complete editor history or an external backup.
#### Backups and recovery
Tornado creates local logical SQL backups and verifies the resulting file with SHA-
256. By default, backup files are stored below the directory returned by `wp_upload_dir()`
in a Tornado-owned directory with a persisted random storage token, restrictive
file permissions, and Apache/IIS deny files. A site administrator may explicitly
provide `SHCD_TORNADO_DBM_BACKUP_DIR` for a custom storage location. A backup records
the Posts ID fingerprint, schema fingerprint, consistency status, and storage classification.
A backup is accepted for reindex only when the required snapshot and protected-storage
checks pass. Mixed storage engines or an insufficiently protected custom backup
location can produce warnings or prevent the backup from being accepted for reindex.
Full database restore is intentionally available through WP-CLI rather than a browser
request, reducing the risk of HTTP timeout or connection loss during import.
#### Important limitations
* Network-wide Multisite reindexing is not supported.
* WooCommerce HPOS order-ID reindexing is not supported.
* Legacy WooCommerce order IDs are not reindexed unless the related advanced option
is explicitly enabled.
* Unknown proprietary data is not rewritten without sufficient evidence or an adapter.
* Remote systems and copied IDs outside the WordPress database cannot be discovered
reliably.
* A successful local backup is not a substitute for an independently tested hosting
or infrastructure backup.
### Privacy
Tornado does not send site data to an external service and does not include usage
tracking or telemetry. Administration requests are made to the site’s own WordPress
REST API.
The plugin stores operational data locally, including settings, discoveries, mappings,
backup records, jobs, logs, revision archives, and short-lived authorization data.
SQL backup files may contain the complete database and must be treated as sensitive
data.
Uninstall removes scheduled events and plugin capabilities. Operational tables and
backup files are removed only when the corresponding uninstall options are enabled
by an administrator.
### Requirements
* WordPress 7.0 or later.
* PHP 8.3 or later.
* A MySQL-compatible database that provides the required `INFORMATION_SCHEMA` metadata.
* InnoDB for every base table in the active database when creating a backup that
will be accepted for reindex.
* Sufficient database privileges for the selected operation. Discovery and cleanup
require fewer privileges than backup, quarantine, restore, or reindex.
* Enough disk space for a complete logical database backup.
### WP-CLI
Tornado registers commands under `wp shcd-tornado-dbm` when WP-CLI is available.
Examples include:
* `wp shcd-tornado-dbm discover`
* `wp shcd-tornado-dbm mapping build`
* `wp shcd-tornado-dbm dry-run `
* `wp shcd-tornado-dbm backup create`
* `wp shcd-tornado-dbm integrity check`
* `wp shcd-tornado-dbm cleanup preview`
* `wp shcd-tornado-dbm cleanup execute --yes`
* `wp shcd-tornado-dbm tables scan-unused`
* `wp shcd-tornado-dbm reindex prepare`
* `wp shcd-tornado-dbm reindex preflight `
Destructive WP-CLI commands require their documented confirmation arguments. Use`
wp help shcd-tornado-dbm` for the commands available in the installed version.
## Screenshots
[[
[[
[[
## Installation
1. Create a full external backup of the site and database.
2. Upload the `shcd-database-maintenance` directory to `/wp-content/plugins/`, or
install the ZIP through Plugins > Add New > Upload Plugin.
3. Activate Shabnam Tornado Database Maintenance.
4. Open Tools > Tornado.
5. Review System Status and run Discovery.
6. Use Preview before any cleanup operation.
7. Test Mapping, Backup, Preflight, and Reindex workflows on a staging copy before
considering production use.
No `wp-config.php` edit is required for normal operation. An optional emergency
constant can disable destructive operations; review the plugin settings and inline
administrator guidance before enabling destructive operations.
## FAQ
### Does Tornado automatically renumber my WordPress posts?
No. Post ID reindexing is disabled by default and requires a separate, explicit
workflow with Discovery, Mapping, Backup, Preflight, authorization, and typed confirmation.
### Do I need reindexing to clean the database?
No. Cleanup, revision retention, orphan checks, backup, integrity reporting, and`
AUTO_INCREMENT` normalization can be used without changing existing Post IDs.
### Does it support a custom database prefix?
Yes. Core table names are read from `$wpdb`, and plugin tables are resolved from
the active `$wpdb->prefix`. The plugin does not hard-code `wp_posts`.
### What is the difference between Post ID reindexing and AUTO_INCREMENT normalization?
Reindexing changes existing IDs and synchronizes registered references. `AUTO_INCREMENT`
normalization changes only the next generated value when the database allows it;
it does not renumber existing rows or remove interior gaps.
### How does adaptive detection handle an unknown plugin table?
It evaluates schema and data evidence before registering a relationship. Clear conventional
references can be included in Preflight and the two-phase mapping. Ambiguous data
remains blocked instead of being rewritten by guesswork.
### Does the plugin support Rank Math?
Version 1.0.0 includes a dedicated Rank Math adapter for supported internal-link,
internal-meta, and analytics object relationships. The adapter is conditional and
only acts on tables and columns that exist in the current installation.
### Does the plugin support Elementor?
It includes structured Elementor reference handling, media repair tools, selected
builder-registry support, and post-operation CSS or cache rebuilding. Elementor
and third-party widget data can vary, so unresolved proprietary paths remain blocking.
### Can Tornado detect IDs stored outside WordPress?
No. Remote services, custom applications, external databases, exported files, and
copied IDs outside the current WordPress database must be audited separately.
### Are backups sent to another server?
No. Backups are created locally. The default location is a protected, randomized
Tornado directory below the WordPress uploads base directory returned by `wp_upload_dir()`.
Administrators remain responsible for server permissions, off-site backups, encryption,
retention, and restore testing.
### Is Multisite supported?
The plugin can inspect the active site’s tables, but network-wide Multisite reindexing
is intentionally not supported. Do not use the reindex workflow as a network-wide
operation.
### What happens when Preflight finds an unresolved reference?
Reindex remains blocked. Review the table and column, choose an explicit supported
policy, register a site-specific adapter, or leave the operation unexecuted.
### What happens when I uninstall the plugin?
Scheduled hooks and Tornado capabilities are removed. By default, operational tables
and backup files are retained to avoid accidental data loss. They are deleted only
when the relevant uninstall settings were enabled before uninstalling.
## Reviews
There are no reviews for this plugin.
## Contributors & Developers
“Shabnam Tornado Database Maintenance” is open source software. The following people
have contributed to this plugin.
Contributors
* [ SHABNAM ](https://profiles.wordpress.org/shcd/)
[Translate “Shabnam Tornado Database Maintenance” into your language.](https://translate.wordpress.org/projects/wp-plugins/shcd-database-maintenance)
### Interested in development?
[Browse the code](https://plugins.trac.wordpress.org/browser/shcd-database-maintenance/),
check out the [SVN repository](https://plugins.svn.wordpress.org/shcd-database-maintenance/),
or subscribe to the [development log](https://plugins.trac.wordpress.org/log/shcd-database-maintenance/)
by [RSS](https://plugins.trac.wordpress.org/log/shcd-database-maintenance/?limit=100&mode=stop_on_copy&format=rss).
## Changelog
#### 1.0.0
* WordPress.org pre-review fixes: standardized backup storage resolution, hardened
protected backup paths and serialized-data handling, and clarified third-party
Elementor option writes.
* Published under the `shcd-database-maintenance` repository slug and matching
text domain.
* Added custom-prefix-aware database discovery using `$wpdb`.
* Added preview-first cleanup, revision policies, orphan checks, and retention
controls.
* Added checksum-verified logical SQL backups with snapshot fingerprints.
* Added immutable Old to Temporary to Final Post ID mapping and dry-run reporting.
* Added controlled, repeatable, gapless Post ID reindex generations with fail-closed
Preflight checks.
* Added dedicated Rank Math reference handling.
* Added conservative adaptive discovery for conventional scalar, polymorphic, structured,
and strict ID-list references.
* Added selected Elementor, Gutenberg, WooCommerce, builder, media, and cache repair
strategies.
* Added reversible table quarantine, audit logs, reports, and WP-CLI commands.
* Added optional independent revision archiving and operational-data retention.
## Meta
* Version **1.0.0**
* Last updated **11 hours ago**
* Active installations **Fewer than 10**
* WordPress version ** 7.0 or higher **
* Tested up to **7.0.4**
* PHP version ** 8.3 or higher **
* Language
* [English (US)](https://wordpress.org/plugins/shcd-database-maintenance/)
* Tags
* [backup](https://az-tr.wordpress.org/plugins/tags/backup/)[cleanup](https://az-tr.wordpress.org/plugins/tags/cleanup/)
[database](https://az-tr.wordpress.org/plugins/tags/database/)[integrity](https://az-tr.wordpress.org/plugins/tags/integrity/)
[reindex](https://az-tr.wordpress.org/plugins/tags/reindex/)
* [Advanced View](https://az-tr.wordpress.org/plugins/shcd-database-maintenance/advanced/)
## Ratings
No reviews have been submitted yet.
[Your review](https://wordpress.org/support/plugin/shcd-database-maintenance/reviews/#new-post)
[See all reviews](https://wordpress.org/support/plugin/shcd-database-maintenance/reviews/)
## Contributors
* [ SHABNAM ](https://profiles.wordpress.org/shcd/)
## Support
Got something to say? Need help?
[View support forum](https://wordpress.org/support/plugin/shcd-database-maintenance/)