Configuration

Move Legacy Custom DB to SlimStat Pro

Applies to SlimStat 6.1.2 and SlimStat Pro 3.1.1 · checked

Version preview: this guide targets Free 6.1.2 and Pro 3.1.1. The last verified public releases are Free 6.0.0 and Pro 3.0.0. Check your download version before following these steps. Review the upgrade guide.

Pro 3.1 can take over the retired Custom DB add-on while keeping analytics in the same external database. It verifies the connection before deactivating the old provider. Existing history is not copied or merged. Back up both the WordPress and analytics databases before changing providers.

Upgrade an active legacy connection

  1. Note which database and table prefix currently contain your history. Keep credentials in a secure place, not a public support ticket.
  2. Update Free to 6.1.2, then install or update Pro to 3.1.1. Keep the active legacy Custom DB add-on in place while Pro verifies the takeover.
  3. Follow the database-provider notice. Pro checks the same database, table ownership, write access and visit counter before saving the connection and deactivating the old add-on.
  4. Verify a newly recorded visit and an older date range. Check that both are using the intended database.
  5. Remove retired add-on files only after the transition is complete and you have verified the results.

The original Custom DB 1.5 ZIP directory is recognized. Legacy databases with an empty table prefix remain supported. A failed verification leaves guidance for the administrator; do not force a new empty connection over existing history.

If the old add-on was already disabled

WordPress may hold newer visits while the external database holds older history. Choose explicitly where future visits should be recorded. Selecting a provider does not move, combine or erase either history.

Disabling the active external database provider can send future visits to the WordPress database. Review that warning before changing the setting. Switching databases safely reseeds the visit counter above existing IDs.

WordPress Multisite

A network-activated legacy add-on stays active until a network administrator completes the transition for every site. A site administrator should not deactivate it for the network. Verify each site’s history, prefix and new tracking after the transition.

What happens during an outage?

  • The external database failing does not terminate WordPress or silently redirect analytics writes to WordPress’s database.
  • Failed connections can retry after 30 seconds. Warnings distinguish interrupted tracking from maintenance problems and clear when the connection recovers.
  • JavaScript tracking can retry through the existing browser queue. Queued hits expire after 30 minutes, depend on the visitor returning, and are not guaranteed to arrive.
  • Server-side tracking has no outage queue. Requests missed while the database is unavailable cannot be assumed recoverable.

An administrator can dismiss a warning for themselves; an ongoing tracking interruption returns after 24 hours. Check the database with your host rather than treating a dismissed warning as recovery.

Does license expiry stop the external database?

Custom DB continues running without an active Pro license. Other Pro features require a valid license activated for the site. Keeping the database provider available prevents a license problem from silently changing where analytics are stored; it does not unlock the other paid tools.

For a new external database, use Pro’s Custom DB settings and Check DB connection. A separate database changes storage, not the fact that WordPress handles tracking requests. See hosting and performance settings and Pro activation.