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.
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.
- Open Databases and identify the database and its owning hosting account.
- Search by the displayed database name or user instead of relying only on the website name.
- Open the appropriate customer user view when creating or changing customer-owned databases.
- Export a database backup before structural edits, maintenance, or removal.
- Use phpMyAdmin for table-level work only after confirming the selected database.
- If rotating a database password, identify all websites and applications using that database user.
- Save the password change and immediately update those application connection settings.
- 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.
- Check that the database and user still appear under the correct account.
- 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.