Build Data Flows from Google Translate to SQL Server using SSIS
Using SQL Server as a backup for critical business data provides an essential safety net against loss. Backing up data to SQL Server enables business users to more easily connect that data with features like reporting, analytics, and more.
This example demonstrates how to use the CData SSIS Tasks for Google Translate inside of a SQL Server SSIS workflow to transfer Google Translate data into a Microsoft SQL Server database.
Add the Components
To get started, add a new Google Translate source and SQL Server ADO.NET destination to a new data flow task.
Create a New Connection Manager
Follow the steps below to save Google Translate connection properties in a connection manager.
- In the Connection Manager window, right-click and then click New Connection. The Add SSIS Connection Manager dialog is displayed.
- In the Connection Manager type menu, select API. The CData Google Translate Connection Manager is displayed.
- Configure connection properties.
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:
- Visit the Google Cloud Console
- Create a new project or select an existing project
- Note down your Project ID (required for all API calls)
- Navigate to "APIs & Services" > "Library"
- Search for and enable the "Cloud Translation API"
- Go to "APIs & Services" > "Credentials"
- Click "Create Credentials" and select "OAuth Client ID"
- Configure the OAuth consent screen if prompted
- Select "Desktop application" or "Web application" as appropriate
- Set the authorized redirect URI (CallbackURL)
- 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
Configure the Google Translate Source
Follow the steps below to specify the query to be used to extract Google Translate data.
- Double-click the Google Translate source to open the source component editor.
- In the Connection Manager menu, select the connection manager previously created.
- Specify the query to use for the data extraction. For example:
SELECT LanguageCode, DisplayName FROM SupportedLanguages WHERE ProjectId = 'my-project-12345'

- Close the Google Translate Source control and connect it to the ADO.NET Destination.
Configure the SQL Server Destination
Follow the steps below to specify the SQL server table to load the Google Translate data into.
- Open the ADO.NET Destination and add a New Connection. Enter your server and database information here.
- In the Data access mode menu, select "table or view".
- In the Table Or View menu, select the table or view to populate.
- Configure any properties you wish to on the Mappings screen.
Run the Project
You can now run the project. After the SSIS Task has finished executing, your database will be populated with Google Translate data.