Skip to content

Databases

Review database servers and perform account-scoped database administration.

1Overview

The administrator database view provides inventory and maintenance access while preserving ownership boundaries. Customer databases, users, storage, and backups belong to their hosting account.

Databases in the administrator panel. Account names, domains, and addresses are examples. Available controls depend on your package and server configuration.
Administrator database inventory with database owners, storage usage, and phpMyAdmin, password, backup, and maintenance actions.

Databases in the administrator panel. Account names, domains, and addresses are examples. Available controls depend on your package and server configuration.

2Before you begin

Administrator actions can affect multiple customer accounts and server services.

3Step-by-step workflow

Use the database list to find the owning account and database, then use the supported management action for user passwords, backups, optimization, or phpMyAdmin access. Let customer-specific work be performed from the user view when possible.

  1. Open Databases and identify the database and its owning hosting account.
  2. Search by the displayed database name or user instead of relying only on the website name.
  3. Open the appropriate customer user view when creating or changing customer-owned databases.
  4. Export a database backup before structural edits, maintenance, or removal.
  5. Use phpMyAdmin for table-level work only after confirming the selected database.
  6. If rotating a database password, identify all websites and applications using that database user.
  7. Save the password change and immediately update those application connection settings.
  8. Test the application and confirm the database and its user remain listed under the correct customer.

4Practical example

Example: changing a database-user password does not automatically update a WordPress configuration file. Plan the password change and application update together to avoid a database-connection error.

5Verify the result

Validate the outcome from the affected account or an independent client connection, not only from the administrator screen.

  1. Check that the database and user still appear under the correct account.
  2. Test the dependent application after password or maintenance actions.

6Common problems and what to check

phpMyAdmin will not open: sign in again and check the private database-tool service status.

Access denied in an application: compare its database host, database name, username, and newly saved password.

Storage looks unexpected: check the individual database inventory and backup files rather than deleting tables based on a summary count.

7Security, impact, and rollback

A database password change affects every application that uses that database user. Export a backup before destructive queries, table repair, or removal.

Related guides

DNS zonesManage local DNS zones and records for hosted domains.App Installers and panel modulesManage Softaculous connectivity and install trusted BigCloudy panel modules.See all guides in Administrator panel

Still need a hand?

Get help with your plan, website, or hosting through your client area.

Open client area