Cloud SQL para MySQL with DBine
How to connect DBine to Cloud SQL para MySQL and what you can do once it's connected. This page is written from what the Cloud SQL para MySQL driver says about itself, so it matches the version of DBine you download.
Connect
- In DBine, open New connection.
- Pick Cloud SQL para MySQL in the list of engines.
- Fill in the fields below, press Test connection and then Save.
Default port: 3306.
General
| Field | Description |
|---|---|
| Server required | Example: localhost |
| Port | |
| Database | |
| Authentication | With AWS IAM, Google Cloud IAM or Entra ID, DBine requests a new token before each connection using this machine's credentials (aws, gcloud or az): no need to paste tokens that expire. They require TLS with a verified server certificate. The user is the database user (the IAM user, the account or the group). Options: Username and password, Google Cloud IAM Default: Username and password |
| Google Cloud account | Optional: the gcloud account that requests the token. Empty: the active one in gcloud (gcloud auth login), the application default credentials or the machine's service account. Example: ana@company.comOnly with Authentication: Google Cloud IAM. |
| User | |
| Password | Password or a pasted IAM token. To stop pasting tokens that expire, choose Authentication → Google Cloud IAM. Kept in the system keychain, never in DBine's files. Only with Authentication: Username and password. |
| Read-only | On or off. |
SSH tunnel. The connection can go through an SSH server, even through a chain of bastions, with a password, a private key or the SSH agent. The server's fingerprint is checked against known_hosts or confirmed the first time.
SSL/TLS
| Field | Description |
|---|---|
| Encrypt the connection (TLS) | Cloud SQL may require TLS; set the instance's server-ca.pem to verify it. Client certificates aren't supported: use the Cloud SQL Auth Proxy if the instance requires them. On or off. |
| Trust the server certificate | On or off. |
| CA certificate (PEM) | Optional, with TLS: the root certificate that signs the server's. A file on this computer. |
What the explorer shows
Under the connection: Databases. Inside each one:
- Tables
- Views
- Procedures
- Functions
- Triggers
Query editor
The editor uses SQL, with completion for the connection's objects. Statements and commands run against the database selected in the tab.
Ready-made templates for new objects:
- New view
- New procedure
- New function
- New trigger
Tools for Cloud SQL para MySQL
Available
- Graphical execution plans
- Live query profiler
- Server monitor
- Sessions and running queries
- End a session
- Locks: who blocks whom
- Cancel another session's query from the sessions list
- Manual transactions (commit and rollback)
- Index usage
- Create databases
- Drop databases
- Database properties
- Relations in the ER diagram
- Visual designer for new objects
- Rename objects
- Compare and sync schemas
- Native bulk load when migrating data
- Users and permissions
Not available for Cloud SQL para MySQL
- Clone tables
- Backups
Why a tool doesn't apply to an engine, and the details of each one, are in the engine support reference.
Generated from the Cloud SQL para MySQL driver 0.1.15, which DBine downloads the first time you connect to Cloud SQL para MySQL.