Maintenance

The Maintenance tab runs the engine’s maintenance commands on tables or collections you pick. The list shows each one’s size and the figures that help you decide, such as dead rows or free space. The exact statement is shown before it runs, and the server’s output after.

Run a command

1. Open Server tools from the connection’s menu and pick Maintenance, or right-click a table in the sidebar or the Objects tab and choose Maintenance….
2. Pick the Database (PostgreSQL), and the Schema (PostgreSQL) or Database (MySQL, MariaDB, MongoDB).
3. Tick the tables or collections. Filter narrows the list.
4. Pick the Command and tick its options.
5. Choose Run … (for example Run ANALYZE…), read the statement, and choose Run.

Commands

Engine	Command	Options
PostgreSQL	VACUUM	FULL, FREEZE, ANALYZE, VERBOSE, SKIP_LOCKED
PostgreSQL	ANALYZE	VERBOSE, SKIP_LOCKED
PostgreSQL	REINDEX	CONCURRENTLY, VERBOSE
PostgreSQL	CLUSTER	VERBOSE; Using index picks the index
MySQL and MariaDB	ANALYZE TABLE	NO_WRITE_TO_BINLOG
MySQL and MariaDB	OPTIMIZE TABLE	NO_WRITE_TO_BINLOG
MySQL and MariaDB	CHECK TABLE	QUICK, FAST, MEDIUM, EXTENDED, CHANGED
MySQL and MariaDB	REPAIR TABLE	NO_WRITE_TO_BINLOG, QUICK, EXTENDED, USE_FRM
MongoDB	compact	force
MongoDB	validate	full

Hover an option to read what it does. REINDEX and CLUSTER take one table at a time; VACUUM and ANALYZE take several. REPAIR TABLE is for MyISAM, Aria, ARCHIVE and CSV tables, not InnoDB.

Locks

VACUUM FULL and CLUSTER rewrite the table and lock it for the duration. Maintenance commands need a confirmation on every profile, and a read-only profile refuses them, except CHECK TABLE and validate, which only read.

Related

• Monitor
• Settings