SleekView for Search Replace DB Pro: rewrite plans & runs as tables
Search Replace DB Pro stores rewrite plans, dry-run counts, and run history in custom option entries. SleekView reads them directly so migration teams can preview affected rows, audit replace pairs, and verify post-run state without leaving WP admin.
♾️ Lifetime License available
Search and replace works. Auditing it is the bigger job.
Search Replace DB Pro extends the standard serialized-aware rewrite engine with saved plans, scheduled runs, and richer audit metadata. Plans and run history live in custom option entries under the srdb_ prefix. The default plugin UI lists plans one at a time, which works for ad-hoc URL rewriting but offers no portfolio-wide view of which plans have run on which environments.
SleekView reads the srdb_ option family directly. Each saved plan becomes a row with name, scoped tables, replace-pair count, last-run timestamp, and dry-run match count visible as columns. A second view exposes the run history with per-run match counts and per-table breakdowns, so audits answer not just "did it run" but "what did it actually change".
For agency teams running multi-environment domain migrations, the audit value sits in the join between plans and runs. Confirm every plan ran on staging before production. Spot plans that returned zero matches (suggesting a stale plan that should be archived). Catch runs whose post-run match count drifted from the pre-run dry-run.
Workflow
Audit every Search Replace DB Pro plan in one workspace
Point at the srdb_ keys
srdb_plans, srdb_runs, and srdb_replace_pairs. The agent samples each and proposes joins so plans, pairs, and runs land in a single workspace.
Flatten the replace pairs
Compare dry-run vs actual
Save audit presets
Sample columns
A typical rewrite plans view
wp_options (keys: srdb_plans, srdb_runs, srdb_replace_pairs)
| Plan | Scope | Pairs | Last run | Matches | Status |
|---|---|---|---|---|---|
| Domain move | wp_posts + wp_postmeta | 5 | Apr 24 | 14,322 | Complete |
| CDN swap | wp_posts | 2 | Apr 22 | 1,284 | Complete |
| HTTPS migration | All tables | 1 | Apr 18 | 412 | Partial |
| Old hostname cleanup | wp_options | 1 | Feb 14 | 0 | Stale |
Comparison
Default Search Replace DB Pro admin vs SleekView
Default Search Replace DB Pro admin
- Saved plans are listed but not jointly auditable with run history
- Post-run verification needs separate SQL queries
- Zero-match runs don't flag stale plans automatically
- Cross-environment audit trails need manual log compilation
- Per-table match breakdowns aren't a sortable column
SleekView
-
Read
srdb_plansandsrdb_runstogether - Join replace pairs to plans in a flat view
- Sort plans by last-run match count
- Filter to zero-match plans for cleanup
- Verify post-run state matches the dry-run prediction
Features
What SleekView gives you for Search Replace DB Pro
Plan-and-run join
Join saved plans to their run history so each plan row shows its most recent matches, per-table breakdown, and outcome. Audits become a single workspace.
Pre/post verification
Compare the dry-run match count to the actual post-run match count. Drift between the two is usually a sign of in-flight content changes during the migration window.
Stale-plan cleanup
Filter plans whose most recent runs returned zero matches across consecutive runs. Those are typically stale plans referencing already-migrated hostnames, ready for archive.
Audience
Who uses SleekView for Search Replace DB Pro
Migration leads
Pre-cutover review confirming every plan has run on staging with the expected match count before the production run happens. Drift between staging and production matches is a red flag.
QA
Post-cutover verification confirming the run actually changed what the dry-run predicted. Zero residual matches on the re-run is the proof QA needs to close the migration ticket.
Agency leads
Audit plan and run inventory across many client installs, with per-environment last-run timestamps visible inline. Useful for retrospectives on multi-site migration projects.
The bigger picture
Why search-replace audits matter more than the run itself
Search-replace migrations are the silent-failure kind: the run completes, the count looks plausible, and the site appears to work. Days later, a customer reports a broken email link, an editor finds a stale CDN URL in a meta description, or a sitemap shows the old domain in a canonical tag. The cost of those misses scales with how late they are caught, and the only reliable defence is verification.
A dry-run count is necessary but not sufficient. A real audit join between plans and runs turns the migration from a one-shot operation into a tracked event with documented pre-run and post-run states. Filter to http, run, refilter, confirm zero matches, export the proof.
The same audit also catches the awkward edge cases that drag-net replaces tend to miss: serialized arrays in postmeta, JSON values in options, hardcoded references in plugin tables. That documented audit habit is what separates a migration that finishes in an afternoon from one that lingers for weeks of cleanup tickets.
Questions
Common questions about SleekView for Search Replace DB Pro
No. Search Replace DB Pro continues to own the actual rewrite engine, including serialized data handling. SleekView is the audit and inventory layer, not a replacement for the run engine.
 Yes for capability-gated users. The plugin exposes a plan-run endpoint that SleekView calls on row actions, so the same hooks fire as a UI-triggered run.
 
Yes. Scheduled plans are stored in the same srdb_plans shape with a schedule field. SleekView surfaces schedule frequency and next-run timestamp as columns for portfolio-wide schedule audits.
Yes. Run history includes per-table match counts, which SleekView exposes as a joinable subview. Per-table drill-downs make verification much faster than scanning raw plugin logs.
 Yes. The two plugins use different option keys, so SleekView can audit both side by side on installs that run a mix of Search Replace DB Pro for scheduled work and Better Search Replace for ad-hoc runs.
 Yes. Reads are non-destructive. Runs trigger through the plugin's own engine, which is the serialized-safe path. Inline plan edits respect plugin setters where available.
 Yes. Both the plans view and the runs view export to CSV, useful for migration retrospectives and for evidence in change-management reviews.
 Yes. Per-subsite plans and runs are aggregated in the same workspace, with subsite blog_id surfaced as a column. Multisite-wide audits become viable without per-subsite drilling.
 Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkoutBrowse more
- Ultimate Membership Pro
- Paid Membership Pro Pro
- Simple Membership
- Members Only
- Lifterlms Pro Membership
- Restrict User Access
- Woocommerce Paid Courses
- User Registration
- Nextend Social Login
- Buddymeet
- Ultimate Membership Pro Indeed
- Restrict User Access Pro
- Ultimatemember Mailchimp
- Super Socializer
- Wp Courseware Members