Database Manager

The Database Manager (vPanel → Databases → Manage on any database card) is a small database browser built into the panel. It lists your tables, shows a table's structure, pages through rows, and runs SQL — without leaving Vanta Panel and without needing phpMyAdmin installed.

It is also linked from the phpMyAdmin page — both as a button beside Open phpMyAdmin and inside the red notice shown when the panel cannot set up your scoped database grant — so it is the fallback when phpMyAdmin is not an option.

How access works

The manager does not connect as your application's database user. It connects as <account>_qik, a scoped user the panel creates and manages for you. On first use the panel generates a 28-character password for it, stores it encrypted, and grants the user access over 127.0.0.1 to each database registered to your account.

That has two consequences worth knowing:

• You never type a database password to use the manager.
• The manager can only see databases the panel knows about. A database that exists in MySQL but was never created or adopted in vPanel will not appear here. Adopt it on the Databases page first.

If the grant cannot be set up, the page says so instead of silently showing an empty list.

Choosing a database

Opening the manager without a database selected shows a tile per database you own. Pick one and you get a two-pane view: your tables down the left with their approximate row counts, and the working area on the right. The breadcrumb at the top takes you back.

Structure and browsing

Selecting a table shows two cards.

Structure lists each column with its type, whether it accepts NULL, its key, and its default. A NULL default is shown as NULL in grey so you can tell it apart from an empty string.

Browse shows the rows, 30 per page, with the true total row count in the heading and Prev/Next links underneath. Long values are shortened in the display so a wide table stays readable; cells holding NULL are labelled as such rather than shown blank.

Running SQL

The Run SQL box takes one statement and runs it against the selected database. What comes back depends on the statement:

• A statement that returns rows shows them in a scrollable table with the column names as headers. Results are capped at 1000 rows — you are told when the result was truncated, so a SELECT with no LIMIT on a large table cannot lock up your browser. Individual values longer than 512 characters are cut with an ellipsis.
• A statement that changes data reports Query OK with the number of rows affected.
• A statement that fails shows MySQL's own error message, unchanged. That is intentional: the exact error is what you need to fix the query.

The panel gives up after 12 seconds if it cannot reach MySQL at all. That is a connection timeout, not a query timeout — a statement that takes a long time keeps running, so put a LIMIT on exploratory queries rather than relying on the panel to cut them off.

You can only do what <account>_qik is allowed to do — anything inside your own databases, and nothing outside them. Server-level statements, other accounts' databases and the MySQL system tables are all out of reach.

What it does not do

The manager is deliberately small. It has no import, no export, no table editor and no row editor. For those:

• To get a dump, use Download on the Databases page — it produces a fresh gzipped mysqldump on demand.
• To import a .sql file, or for anything the manager does not cover, use phpMyAdmin.