MySQL, MariaDB, PostgreSQL and MSSQL Management

Choose the engine for the application

Identify supported engine versions, character sets and drivers. A SQL export is not necessarily portable to a different engine: syntax, data types and account management differ.

Customer database limits count databases across all engines. Record the site/database ownership relationship explicitly; similar names do not prove shared ownership. This relationship also helps organize backups under the correct resource.

Connecting the application

Verify the required engine is installed and its service is running.
Create the database within the customer’s scope and quota.
Create a dedicated application account with a strong password and only the needed database permissions.
Set server address, engine port, database name and credentials in the application’s protected configuration.
Connect from the service account and network environment that actually run the application.
Test reading, a controlled write operation and any schema migration, then take a backup.

Using phpMyAdmin and Adminer

Use the panel’s database tool entry where the tool is installed and the connection is supported. Credentials created by the panel are stored encrypted so management can use the relevant account’s database permissions. Avoid sharing a common root account with customers.

Opening a web administration tool does not prove the application can connect: the tool may use another account or address. Compare connection settings without putting passwords in screenshots, support tickets or command history.

When is remote access necessary?

An application on the same server generally does not need the database exposed to the internet. For remote access, consider allowed sources, listening addresses, firewall rules and encrypted connections together. Opening a port alone does not grant database permissions.

A timeout can indicate a network or listening problem; authentication rejection concerns the account or method; an access-denied error may concern object permissions. Use the engine log and actual error code to identify the stage.

What proves a backup can be restored?

Select databases explicitly when creating a site backup. A files-only archive is not a database backup. Restore the export into a separate test database and run application queries against it. Accounts and credentials must also work on the destination server; moving data does not always transfer account permissions.