Inspect, diagnose, export, and restore project databases

The job to be done

Inspect and back up the project's database from the project itself

Local database work often lives in a separate client with its own saved connections, while migrations run in a terminal and backups end up in whatever folder was open. Before a risky migration you want the schema, a few records and a fresh backup of the same database, and you want to be sure which database that is.

With DevDock Pro, the Database tool sits inside the project. A detected Laravel project connects through its own .env settings, and any SQLite, MySQL/MariaDB or PostgreSQL database can be added as a direct connection for the session. From there you browse the schema, look up records, and export or import native backups.

For Laravel connections, migration review, diagnostics, seeding and wiping run as project commands. Their output is saved in Run History with the rest of the project's work.

Recommended path

Back up, review, then change the schema

A safe order for running a migration against a local or test database.

1. Open the right connection

   Open Database in the project's Tools menu. Use Project (.env) for a Laravel app, or choose Add database and run Test connection until it shows Connection verified.

2. Look before changing anything

   Use Search schema in the Schema browser to find the tables involved, then Find records with a table, an optional exact value and a small row limit.

3. Export a backup

   Choose Export backup. SQLite uses its built-in backup, MySQL and MariaDB use mysqldump, and PostgreSQL uses pg_dump.

4. Review pending migrations

   In a Laravel project, run Pending migrations under Checks & diagnostics to see which migration files are not applied yet. Then start Run migrations from Commands.

5. Read the result

   Open Run History to read the migration output and exit code. If something went wrong, restore the database with Import backup after checking the target connection.

Capabilities involved

The DevDock tools used for database work

Limits to know

Plan, tools and safety limits

The Database tool is part of DevDock Pro. SQLite needs no extra software. Direct MySQL/MariaDB connections need the mysql and mysqldump clients installed, and PostgreSQL connections need psql and pg_dump.

Pending migrations, Table sizes, Slow tables, Seed database and Wipe database appear only for a connection read from a detected Laravel project's .env file. Laravel refuses Slow tables and Import backup unless the application environment is local or testing.

Record lookups take one table, one optional exact-value filter and at most 200 rows. Arbitrary SQL is not accepted.

Passwords for direct connections last for the current session only, so you enter them again after restarting DevDock.

Related manual

Database tools, schema inspection, and backups

Use DevDock with SQLite, MySQL/MariaDB, PostgreSQL, and detected Laravel databases for safe lookups, schema review, diagnostics, exports, and confirmed restores.

Its sections cover choose the project or direct connection, understand the supported database engines, inspect schema before querying, find records with a constrained lookup, export and restore native backups, use laravel diagnostics and maintenance, troubleshoot without weakening safety. Use it when you are ready to reproduce this workflow with your own project data.

Direct answers

Questions about this use case.