EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB299897: How to configure the MicroStrategy Google BigQuery ODBC Driver in Linux with MicroStrategy Secure Enterprise


Community Admin

• Strategy


This technical note explains how to generate a refresh token to connect to Google Big Query in Linux, with MicroStrategy Secure Enterprise.

The following steps explain how to generate a refresh token to connect to Google Big Query from a Linux environment, with an ODBC connection:

  1. Copy the get_refresh_token.txt file attached to this document, to a directory (for example, /opt/Strategy) on the Linux Intelligence Server machine where the Strategy Google BigQuery ODBC driver DSN will be created, and rename it to get_refresh_token.sh. 
  2. Make the get_refresh_token.sh file executable by running the following command:
     "chmod +x get_refresh_token.sh".  This script will be used later in the DSN creation process.
  3. Open the Strategy odbc.ini.example file and locate the example DSN for the Strategy Google BigQuery ODBC Driver.
ka0PW0000000hD3YAI_0EM440000002J9O.jpeg
ka0PW0000000hD3YAI_0EM440000002J9M.jpeg


         4. Copy the example DSN entries from the odbc.ini.example file into the Strategy odbc.ini file.  

ka0PW0000000hD3YAI_0EM440000002J9z.jpeg


        5. Update the Strategy Google BigQuery ODBC driver DSN in the odbc.ini file to add the name of the Google BigQuery project in the Catalog entry of the DSN. Be weary, the Catalog parameter is case sensitive.  (Note:  If needed, also update the ExecCatalog entry to include the name of the project to bill for queries that are run.) 
*The following Google documentation explains how to find the Google BigQuery Project ID to use in the Catalog/ExecCatalog entries of the DSN.

ka0PW0000000hD3YAI_0EM440000002JA1.jpeg


        6. The Strategy Google BigQuery ODBC driver DSN requires a refresh token prior to connecting.  Generate this refresh token to authorize the connection to BigQuery by following the steps below.
             a. Open an Internet browser and go to the following URL
            b. Type the credentials for accessing your BigQuery data, and then click Sign in.
            c.  When prompted to allow BigQuery Client Tools to access data in Google BigQuery, click Accept, and then copy the code that Google provides.
            d.  To generate the refresh token, run the get_refresh_token.sh shell script provided in the first step in this tech note, passing in the code that was copied in step c.  For example, 
/get_refresh_token.sh YourCodeFromGoogle
YourRefreshTokenWillGoHereAfterYouGenerateItFromGoogle/get_refresh_token.sh
            e.  Copy the refresh token from the output of the script. The refresh token is the text on the right side of the colon with no leading or trailing spaces.
/get_refresh_token.sh YourRefreshTokenWillGoHereAfterYouGenerateItFromGoogle
refresh_token : YouWillFindTheRefreshTokenHereAndWillCopyThisToTheDSN
            f.  In the odbc.ini file, set the RefreshToken value for the Strategy Google BigQuery DSN by pasting in the refresh token that was copied in step e.

ka0PW0000000hD3YAI_0EM440000002JA3.jpeg


     
      7. Save the odbc.ini file and exit.
       8. Open the Strategy DB Query tool and test the connection to Google BigQuery with the newly created DSN.

ka0PW0000000hD3YAI_0EM440000002JA6.jpeg


KB299897


Comment

0 comments

Details

Knowledge Article

Published:

June 6, 2017

Last Updated:

February 13, 2024