![]() |
VOOZH | about |
MicroStrategy is an analytics and mobility platform that enables data-driven innovation. When you pair MicroStrategy with the CData ODBC Driver for Google Translate, you gain database-like access to live Google Translate data from MicroStrategy, expanding your reporting and analytics capabilities. In this article, we walk through adding Google Translate as external data in MicroStrategy Web and creating a simple visualization of Google Translate data.
The CData ODBC driver offers unmatched performance for interacting with live Google Translate data in MicroStrategy due to optimized data processing built into the driver. When you issue complex SQL queries from MicroStrategy to Google Translate, the driver pushes supported SQL operations, like filters and aggregations, directly to Google Translate and utilizes the embedded SQL engine to process unsupported operations (often SQL functions and JOIN operations) client-side. With built-in dynamic metadata querying, you can visualize and analyze Google Translate data using native MicroStrategy data types.
Information for connecting to Google Translate follows, along with different instructions for configuring a DSN in Windows and Linux environments (the ODBC Driver for Google Translate must be installed on the machine hosting the connected MicroStrategy Intelligence Server).
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.
To set up OAuth authentication:
The Google Cloud Translation API Profile requires the following OAuth scope:
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.
If you have not already, first specify connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs.
If you are installing the CData ODBC Driver for Google Translate in a Linux environment, the driver installation predefines a system DSN. You can modify the DSN by editing the system data sources file (/etc/odbc.ini) and defining the required connection properties.
[CData API Sys] Driver = CData ODBC Driver for Google Translate Description = My Description Profile = C:\profiles\GoogleTranslate.apip AuthScheme = OAuth InitiateOAuth = GETANDREFRESH OAuthClientId = your_client_id OAuthClientSecret = your_client_secret CallbackUrl = your_callback_url
For specific information on using these configuration files, please refer to the help documentation (installed and found online).
Once you have created a database instance in MicroStrategy Developer and connected it to a project, you can perform a data import of Google Translate data from MicroStrategy Web. Alternatively, you can create a new data source based on the ODBC Driver.*
SELECT CatalogName NAME_SPACE, TableName TAB_NAME FROM SYS_TABLES
SELECT DISTINCT CatalogName NAME_SPACE, TableName TAB_NAME, ColumnName COL_NAME, DataTypeName DATA_TYPE, Length DATA_LEN, NumericPrecision DATA_PREC, NumericScale DATA_SCALE FROM SYS_TABLECOLUMNS WHERE TableName IN (#TABLE_LIST#) ORDER BY 1,2,3
Using the CData ODBC Driver for Google Translate in MicroStrategy Web, you can easily create robust visualizations and reports on Google Translate data. Read our other articles on connecting to Google Translate in MicroStrategy and connecting to Google Translate in MicroStrategy Desktop for more examples.
Note: connecting using a ODBC driver requires a 3- or 4-tier architecture.
Connect to live data from Google Translate with the API Driver
Connect to Google Translate