Create a named application database inside an existing managed MySQL instance. This does not provision another Cloud SQL instance or select the application’s database user automatically.

Open the intended service

Sign in to the client area, open the intended MySQL service and choose Manage. Use that service’s module tabs for the sections below. Confirm the service and resource before making a change. Enable the corresponding client feature on the intended offering. If a section is missing or unavailable, review that service’s configuration rather than trying a different service.

Choose the application database name

Open Databases, or Manage databases from the overview. Check the existing list and any pending operation before adding another entry.

Names must start with a letter and contain letters, numbers, underscores or dashes, up to 63 characters. Reserved system databases cannot be created through this control. Choose a name the application will use consistently. A database name with a dash can need appropriate identifier quoting in SQL tools.

Add the database

1. Enter the intended database name in the name field.
2. Choose Add database.
3. Read the result and allow the provider operation to finish.
4. Reload the list and confirm the intended database appears before repeating the action.

A newly created database is not an imported application schema or restored backup. Deploy the application’s schema and data through its normal process. Creating the database does not choose a login or configure database-specific grants.

Connect the application

Configure the application with this exact database name, its intended user, the actual connection host and port, the allowed network source and the correct TLS verification. Have the database administrator review the required user permissions, then test the application against the intended database.

The module’s connection panel can show the instance administrator credential without an application database name. Do not assume that this means an application database already exists or that the administrator login is the desired application account.

Check the outcome

Wait for the provider operation to settle, then reload the relevant section and verify the actual result. A success notice or Done activity row can precede final provider completion. If an operation is already in progress, wait rather than repeatedly submitting it.

An empty list can also result from a failed read; it does not establish that the resource has no entries. For an uncertain result, reconcile the service and provider state before repeating a change. Do not include passwords, provider keys or full customer records.

See the PD Google Cloud MySQL Blesta guide for related setup, or explore PD Google Cloud MySQL.