MySQL databases
A real database for your plugins or your bot. Credentials, where they work, and what happens when you delete.
2 min read
On this page
Create
In the Databases tab, Create database creates one. How many you can have is shown at the top under Database slots; if your plan includes none, the page says so. You immediately get host, port, database, user, password and a ready-made connection URL. The details stay in the list afterwards, with the password hidden behind Show password.
Only the owner of the server sees this tab. The user has permissions on exactly this one database and no other. The number of concurrent connections is limited, so that a misconfigured connection pool cannot block the server for everyone else.
Enter it in a plugin
Most plugins ask for exactly these five details. Enter them as they appear in the interface.
host: mysql.citexnode.de
port: 3306
database: cn_xxxxxxxx
username: cn_xxxxxxxx
password: (from the interface)This is the general shape; your real values are under Databases on your server. Database name and user name are the same.
Connect from home
Same host, same port, same credentials. HeidiSQL, DBeaver, TablePlus or your IDE's MySQL plugin connect directly. Turn on SSL in the client if it offers it: your password never crosses the line in plain text either way, but your queries and your data do, as long as you do not use SSL.
Delete
If you delete the database, all tables and data in it are gone for good. If you delete the server, its databases go with it. A backup of your server does not include the database, which lives elsewhere; a dump from your client is your backup.