The Database Toolkit, under Tools → DB Check, identifies database-related issues and fixes them automatically. It has two functions: running migrations to sync your database schema with the current Mumara version, and checking that all tables have the required indexes for fast queries.
Clicking Run Migrations clears the migration tracking history and re-runs all migration files from the beginning, applying any missing tables, columns, or constraints. Use it after updating Mumara, after restoring from a backup, when you hit "table not found" or "column not found" errors, or when support recommends it. The operation is designed to be safe — it adds missing elements without destroying existing data — but always keep a current backup before running it in production.
The collapsible Database Indexes section checks every table in realtime against your actual database structure. Tables with all required indexes show a green "INDEXED" badge; tables with missing indexes can be fixed individually with the apply button next to each one, or all at once via Apply All. Missing indexes are a common cause of slow page loads, timeouts on large lists, and high database CPU usage, so this is worth checking whenever performance degrades.
Worth knowing: applying indexes requires the database user to have CREATE INDEX privilege and enough disk space; if migrations or indexes fail, check Debug Logs for the specific error and retry during a low-traffic period.
