Every WordPress site needs a database, and Kelma creates one for you automatically when you launch a site. But you can also create extra databases — for a second app, a staging copy, or a custom integration — and manage them entirely from the panel. This guide covers creating databases and users, browsing your data, and deleting safely.
Create a database
- Open your site and go to the Databases tab.
- Enter a database name, a database user, and a strong password.
- Click Save. The database and its user are created and ready to use immediately.
shop_prod and shop_staging — so you never point the wrong site at the wrong data.Open phpMyAdmin
Click One-Click phpMyAdmin to open a live session for your server — no separate login required. From there you can browse tables, run SQL queries, search and edit individual rows, and import or export data. It is the fastest way to inspect what is actually stored in your site.
Import and export
- Export a full
.sqldump before any risky change, or to move a site elsewhere. - Import an existing database when migrating in — pick the target database, then upload the file.
- For very large databases, importing over SFTP and the command line is more reliable than the browser uploader; our team can help if you get stuck.
Connecting WordPress to a database
If you are wiring up a database manually, WordPress reads its connection details from wp-config.php — the DB_NAME, DB_USER, DB_PASSWORD, and DB_HOST constants. Use the credentials you set when creating the database. The host is almost always localhost because the database runs on the same server as your site.
Deleting a database
Use the delete icon next to any database to remove it. This is permanent and cannot be undone, so make sure you have a current backup of anything you might need first. Deleting a database does not delete the site files — only the data.
Database best practices
A few habits keep your data tidy and safe. Give every project its own database and user rather than sharing one across sites — it keeps things isolated and makes restores painless. Use a long, unique password for each database user. Export a fresh dump before any structural change, plugin that modifies the schema, or large content import. And keep your database lean: deactivating and deleting unused plugins removes the tables and options they leave behind, which keeps backups small and queries fast.
Frequently asked
What database host should WordPress use?
Almost always localhost, because the database runs on the same server as your site. Set it as DB_HOST in wp-config.php alongside the database name, user, and password.
How do I reset a database password?
Update the user is password on the Databases tab, then change the matching DB_PASSWORD value in wp-config.php so WordPress can still connect.
My site shows error establishing a database connection — what now?
That means the credentials in wp-config.php no longer match the database. Confirm the name, user, password, and host, and check that the database still exists. If you are unsure, our team can diagnose it in chat.
In short
Your site is database is created for you, but the panel puts full control at your fingertips: create extra databases and users, open phpMyAdmin in one click to inspect or query your data, and import or export complete dumps when you migrate or test. Treat the database as the most precious part of your site — back it up before structural changes, give each project its own isolated database, and use strong, unique passwords. With those habits, working directly with your data is safe rather than scary.
Leave a Reply