Access Google Translate Data from MySQL in HeidiSQL

HeidiSQL is an open-source database administration tool that natively supports MariaDB, MySQL, SQL Server, and PostgreSQL. When paired with the CData API Driver for ODBC and SQL Gateway, HediSQL's reach extends to include access to live Google Translate data. This article demonstrates how to connect to on-premise Google Translate and query Google Translate data in HeidiSQL.

Connect to Google Translate Data

If you have not already done so, provide values for the required connection properties in the data source name (DSN). You can use the built-in Microsoft ODBC Data Source Administrator to configure the DSN. This is also the last step of the driver installation. See the "Getting Started" chapter in the help documentation for a guide to using the Microsoft ODBC Data Source Administrator to create and configure a DSN.

Authentication

Google Cloud Translation API requires OAuth 2.0 authentication to ensure secure access to translation services, datasets, glossaries, and adaptive MT resources. This authentication method allows you to securely connect to your Google Cloud project and manage translation resources with proper authorization.

OAuth 2.0 Setup and Configuration

Step 1: Create Google Cloud Project and Enable API

To set up OAuth authentication:

1. Visit the Google Cloud Console
2. Create a new project or select an existing project
3. Note down your Project ID (required for all API calls)
4. Navigate to "APIs & Services" > "Library"
5. Search for and enable the "Cloud Translation API"
6. Go to "APIs & Services" > "Credentials"
7. Click "Create Credentials" and select "OAuth Client ID"
8. Configure the OAuth consent screen if prompted
9. Select "Desktop application" or "Web application" as appropriate
10. Set the authorized redirect URI (CallbackURL)
11. Copy the Client ID and Client Secret for use in your connection

Required Connection Properties

• AuthScheme: Set this to OAuth (required)
• OAuthClientId: Client ID from Google Cloud Console (required)
• OAuthClientSecret: Client secret from Google Cloud Console (required)
• CallbackURL: Redirect URI specified in your OAuth application (required)
• InitiateOAuth: Set to GETANDREFRESH for automatic token management (recommended)
• ProjectId: Your Google Cloud project ID or project number (required for queries)

Required OAuth Scopes

The Google Cloud Translation API Profile requires the following OAuth scope:

• https://www.googleapis.com/auth/cloud-translation - Full access to Cloud Translation API resources including translation, datasets, glossaries, and adaptive MT

When you configure the DSN, you may also want to set the Max Rows connection property. This will limit the number of rows returned, which is especially helpful for improving performance when designing reports and visualizations.

Configure the SQL Gateway

See the SQL Gateway Overview to set up connectivity to Google Translate data as a virtual MySQL database. You will configure a MySQL remoting service that listens for MySQL requests from clients. The service can be configured in the SQL Gateway UI.

👁 Creating a MySQL Remoting Service in SQL Gateway (Salesforce is shown)

To connect to the SQL Gateway from HeidiSQL, you will need to run the SQL Gateway on a web-facing machine. After configuring the SQL Gateway, make note of the following information:

• The IP address or domain name of the machine hosting the SQL Gateway
• The data source name (likely CData API Sys) of the MySQL service
• The port number of the MySQL service
• The credentials of a SQL Gateway user with access to the service

Configure Remote Access

If your ODBC Driver and the remoting service are installed on-premise (and not accessible from HeidiSQL), you can use the reverse SSH tunneling feature to enable remote access. For detailed instructions, read our Knowledge Base article: SQL Gateway SSH Tunneling Capabilities.

Connect to Google Translate in HeidiSQL

Once you have a MySQL Service configured for the CData API Driver for ODBC, you are ready to connect to the data in HeidiSQL. Start by creating a new connection Session in HeidiSQL, then choose the MySQL library type.

Configure the data set using the values for the MySQL service for Google Translate you configured in SQL Gateway (be sure to use the DSN for the database name). Validate your connection and click Open.

👁 Configure the connection to SQL Gateway.

Query Google Translate from HeidiSQL

1. In the database listing on the left, find your connection to Google Translate configured earlier.
2. In the database listing on the left, expand the appropriate connection and to view individual tables or data objects present within Google Translate.
3. Write custom SQL queries targeting these tables, treating the data source like any SQL Server database, or visually explore each tabular data set by selecting the relevant tables 👁 Querying within HeidiSQL.
   

With the CData API Driver for ODBC and SQL Gateway, you are able to easily query data from Google Translate data in HeidiSQL. If you have any questions, such as needing to access your on-premises data from HeidiSQL, let our Support Team know.