Our Web Hosting management tools support database administration for the database services enabled on your account. Typical tasks include creating a database, creating a database user, assigning access and updating a user's password. MySQL or a compatible service is commonly used by website applications. Other database types and management interfaces depend on the package and server, so confirm availability before selecting software that requires a particular database engine.
IN THIS ARTICLE
01 Create the database connection your application needs
- When setting up an application, create or identify its database, associate the correct user and grant the privileges the application requires.
- Use the exact database name, username, host and credentials provided by the account.
Hosting systems may add an account prefix to database and user names, so a shortened name copied from an installation example can cause connection failures.
02 Protect data before imports and access changes
Before importing data, changing a schema or editing live records, make a usable backup and identify which website depends on the database. A database management interface such as phpMyAdmin, where provided, exposes powerful operations. Deleting a table or importing an old copy can remove current content, orders or customer records. Test significant changes on a suitable non-production copy and follow the application's own update process wherever possible.
Changing a database user's password requires updating the affected application's connection settings as well. Otherwise, the site may lose access even though the database remains intact. Assign access deliberately instead of sharing one broadly privileged user across unrelated projects. If remote database connections are available, permit only the required trusted source addresses and remove unused access. If you see a connection error, check the application's configuration and the user's assigned access before recreating or deleting anything. Provide the error text to us with credentials and customer data removed.
03 Example: match the application to the complete database details
Suppose your account lists a database named acct_shop and an assigned user named acct_shopuser. These names are illustrative. Copy the complete values shown for your own account into the application's private connection settings.
| Application field | What to enter |
|---|---|
| Database name | The full database name, such as acct_shop, including its prefix. |
| Database user | The full assigned username, such as acct_shopuser, with the required privileges on that database. |
| Database host | The host supplied for this service. Copy its actual value instead of borrowing another application's setting. |
| Password | The current password for this database user, entered privately. It is not automatically the client-area or website-administrator password. |
Verify a page that reads or writes the intended application data. A successful phpMyAdmin session alone does not verify these application settings.
How do I verify a database-user or permission change?
- Identify the database and its assigned user before altering either resource.
- Record the exact account-prefixed names and host, then grant only the privileges the application requires.
- If changing a password, update the application's private connection configuration and test a database-dependent page.
A successful login to phpMyAdmin does not establish that the application uses the same credentials or database. Preserve a current database copy before imports and schema changes. When reporting a connection problem, share the error text and affected application without the password or a full customer-data export.