Manage Databases — Simple & Complete Guide

Manage Databases — Simple & Complete Guide

Manage Databases — Simple & Complete Guide

This page shows every database managed by user accounts on your server. You can see which account owns each database, the database engine (MySQL or MariaDB), search and sort the list, and rename a database when needed.

Note: In recent versions, this tool appears under Database Services.

Important limits & warnings
  • Maximum database name length is 64 characters. If database prefixing is enabled, the prefix and underscore count toward this limit; each underscore consumes two characters in how names are stored.
  • Renaming is potentially disruptive: active connections will be terminated, apps may break until configs are updated, and large databases take longer to process.
  • Always make a backup before renaming.

Browse, Search, and Sort

  • Use the search box to find a database by name.
  • Click any column header to sort (for example by database name, engine, or owner).

Rename a Database

  1. In the table, click the edit (pencil) icon for the target database.
  2. Enter the new database name in the field provided.
    Note: If prefixing is enabled for the owning account, include the required prefix (for example, user_newdbname).
  3. Click Submit to begin the rename.

What actually happens during a “rename”

Because MySQL/MariaDB do not natively rename databases, the system performs a safe copy-and-swap:

1) Create a new database with the target name
2) Copy the data from the old database into the new one
3) Recreate grants and stored code (procedures/functions/triggers)
4) Delete the old database and its grants
Heads-up: If any of the first three steps fail, the system returns an error and attempts to roll back. In rare cases, the old database may remain and you’ll see warnings indicating what could not be deleted. Check the messages and take any suggested follow-up actions.

After the rename

  • Update application configuration files to use the new database name (CMS, frameworks, env files, etc.).
  • Verify the site/app connects and runs queries normally.
  • If the database is large or busy, expect the process to take longer.

Safety Checklist

  • Create a full backup or dump of the database before starting.
  • Schedule a maintenance window for busy sites.
  • Confirm you have the correct new name (including any required prefix).
  • Have app credentials/configs ready to update immediately after the change.

Quick Example: Update an App Config

Replace the old DB name with the new one in your application’s configuration file (example syntax only):

# .env or config.php example
DB_HOST=localhost
DB_NAME=new_database_name
DB_USER=the_user
DB_PASS=the_password

Summary

  • View all databases with their engine and owner; search and sort the list.
  • Rename a database safely using the built-in copy-and-swap process.
  • Know the limits (name length/prefixing) and impact (connections, app configs).
  • Back up first, then verify apps after the rename.

Reference: Official “Manage Databases” documentation (overview, limitations, search/sort, rename steps, and internal rename process).

case studies

See More Case Studies