Skip to Content
Browse documentation

MySQL Servers

Review registered MySQL servers, toggle usage status, request a soft restart and remove remote connections.

Open Database Engines → MySQL → MySQL Servers.

Server table

The table displays Server, server type, version, local/remote location, Enabled/Disabled usage status and Actions. These are registration values, not continuous connection or service-health probes.

Use search, sorting and pagination to find the host. Add Remote MySQL Server opens the registration form. Remote rows also provide Edit connection.

Enable or disable usage

  1. Click the host's enable/disable control.
  2. Review the host and usage warning.
  3. Confirm Enable Server or Disable Server.
  4. Check the updated status and intended database-management behavior.

The helper changes the saved usage flag only. The UI describes disabled servers as unavailable for creating databases. It does not stop MySQL, disconnect clients, revoke database grants or move existing databases.

Soft restart

Click Soft restart, check the host and confirm Restart Server. The helper connects using saved credentials and issues the SQL RESTART statement.

A restart request is not a completed health check

The database implementation must support the command and the saved account must be authorized to use it. Connections can be interrupted. A successful request does not prove the server returned to service; verify connectivity and applications afterward.

Connection or command failures can both appear as connection errors. Inspect the actual server and logs rather than repeatedly requesting restarts.

Remove a remote server

  1. Review databases and accounts managed through the host.
  2. Resolve dependencies and retain the connection details securely.
  3. Click Delete server on the remote row.
  4. Review the confirmation and click Delete Server, or Cancel.
  5. Verify panel management and affected consumers.

The local localhost entry is protected from removal. Removing a remote entry deletes its saved panel authentication/registration data; it does not drop databases, remove remote users or stop the remote service. It does not automatically migrate any data.

There is no consumer-aware migration in this removal helper. It can remove authentication data before a later preference update fails, so investigate partial state before retrying.

Demo sessions cannot change status, restart or remove entries.