Google BigQuery for RED 8

This is a guide to installing the WhereScape Enablement Pack for Google BigQuery for WhereScape RED 8.6.6.+ 

Prerequisites

Before you begin the following prerequisites must be met:

1. A supported* version of SQL Server or Azure SQL with
   • Database created  to house the RED Metadata Repository with 'SELECT', 'INSERT', 'UPDATE', and 'EXECUTE' permissions
   • (optionally) a database for the Range Table DB
   • ODBC DSN's created for these DB's 
2. A BigQuery environment with
   • At least one schema available to use as a RED Data Warehouse Target
3. BigQuery software installed
   • BigQuery ODBC driver (64-bit) Simba ODBC driver 2.05.00.1001 or higher.
   • Google Cloud SDK for utilities GSUTIL and BQ installed and on the Windows system path
     • Download and Install Google Cloud SDK Installer from {+}https://cloud.google.com/sdk/docs/quickstart+
     • Note: To use the Google Cloud SDK and its associated tools (GSUTIL and BQ), authentication, initialization, and project configuration are required. Please refer to the provided instructions for completing this process from {+}https://cloud.google.com/sdk/docs/install-sdk+
     • Important: Google Cloud SDK and its associated tools (GSUTIL and BQ) must be authenticated again after installation. For reauthentication please refer to this process from {+}https://cloud.google.com/sdk/gcloud/reference/auth/application-default/login+ or run the below command as admin in Command Prompt and follow the prompted instructions.  A complete system restart is recommended after this process.
       

       gcloud auth application-default login

• • ODBC DSN created to connect to your RED Data Warehouse on BigQuery
  • Google BigQuery Catalog Name
  • At least one storage bucket needs to be created on Google Cloud Storage.
    • Permission Required: Upload, Read and Delete File

1. WhereScape RED version 8.6.6.0 or higher
   • Must be pre-installed with valid license key entered and EULA accepted
2. WhereScape Enablement Pack for BigQuery version 8.6.6.0 or higher
   • Downloaded and unpacked to a local temp folder
3.  Python 3.8 or higher
   • Download Python installer from {+}https://www.python.org/downloads/+
   • Select "Add Python 3.8 to PATH" from the installation Window
   • PIP Manager
   • From Command Prompt (Run As Administrator) run below command
     
     PIP Manager Install

     python -m pip install --upgrade pip

• RED supports the following versions for the metadata repository: MS SQL SERVER 2012 to 2019 and Azure SQL DB

Enablement Pack Setup Scripts

Scripts entirely drive the Enablement Pack Install process. The table below outlines these scripts, their purpose, and if Run as Administrator is required. 

Each Powershell script in the list above provides some help at the command line, this can be output by passing the "-help" parameter to the script.

Step-By-Step Guide

Setup and configure a new RED Metadata Repository for BigQuery

Run Powershell as Administrator:

Script 1 > Powershell -ExecutionPolicy Bypass -File .\Setup_Enablement_Pack.ps1

Install or Update WhereScape Powershell Modules

Run Script As Administrator

Script 2 > install_WslPowershell_Modules.bat

Install or Update WhereScape Python Modules

Run Script As Administrator

Script 3 > install_WslPython_Modules.bat

 There are two steps in this script:

1. Installs the WhereScape WslPython modules to C:\Program Data\WhereScape\Modules\
2. PIP to download/update required Python libraries - for offline install please see the required library list for Python in the Troubleshooting section.

Install or Update WhereScape Python Templates (For Existing Installations)

Run Script as Administrator

        Script 1 > install_WslPython_Modules.bat
        Script 2 > import_python_templates.ps1
        Script 3 > set_default_templates.ps1

Note: Skip this step for new installations.

Set Connection defaults for a Template Set (For Existing Installations)

Script 1 > set_default_templates.ps1 

Choose Python when prompted

Post Install Steps - Optional

If you used the script 'Setup_Enablement_Pack.ps1' then the following optional post-install steps are available

Configure Connections

There were two connections added that will optionally require your attention:

1. Connection: 'BigQuery' - This connection was set as per parameters provided in the installation script 1
   1. open its properties and check the extended properties tab, set it up for LOCATION. Ignore if already set during the installation script prompt
2. Connection: 'Database Source System' - this connection was set up as an example source connection,
   • open it's properties and set it up for a source DB in your environment
   • or you can remove it if not required

Enable Script Launcher Toolbar

Several stand-alone scripts provide some features, these scripts have been added to the Script Launcher menu but you will need to enable the menu toolbar item to see them.
To enable the Script Launcher menu in RED: Select menu item View>Toolbars->Script Launcher

Service Authentication

A User DSN must be created for both the repository user and each user, as these references utilize a single, one-time-use key.
If a User DSN cannot be created for the repository user, a System DSN can be used as an alternative
To update the 'Services' settings if jobs are not running through the scheduler, please follow the steps shown in the attached screenshots:

Source Enablement Pack Support

Troubleshooting and Tips

Run As Administrator

Press the Windows Key on your keyboard and start typing cmd.exe, when the cmd.exe icon shows up in the search list right click it to bring up the context menu, select Run As Administrator
Now you have an admin prompt navigate to to the folder where you have unpacked your WhereScape Red Enablement Pack using the 'cd' command:
C:\Windows\system32> cd <full path to the unpacked folder> 
Run batch (.bat) scripts from the administrator prompt by simply typing the name at the prompt and clicking enter, for example:
C:\temp\EnablementPack>install_WslPowershell_Modules.bat
Run Powershell (.ps1) scripts from the administrator prompt by typing the Powershell run script command, for example:
C:\temp\EnablementPack>Powershell -ExecutionPolicy Bypass -File .\Setup_Enablement_Pack.ps1

Windows Powershell Script Execution

On some systems, Windows Powershell script execution is disabled by default. There are several workarounds for this which can be found on the internet by searching the term "Powershell Execution Policy".
Here is the most common workaround that WhereScape suggests, which does not permanently change the execution rights:
Start a Windows CMD prompt as Administrator, change the directory to your script directory, and run the WhereScape Powershell scripts with this command:

• cmd:>Powershell -ExecutionPolicy Bypass -File .\<script_file_name.ps1>

Restarting failed scripts

Some of the setup scripts will track each step and output the step number when there is a failure. To restart from the failed step (or to skip the step) provide the parameter -startAtStep <step number> to the script.
Example: 
Powershell -ExecutionPolicy Bypass -File .\<script_file_name.ps1> -startAtStep 123

Python requirements for offline install

Additionally to the base Python installation being required, the WhereScape Python Template set also requires certain additional Python libraries. The install scripts use the PIP (package manager) to download these libraries, however, for offline installs, you will need to install the required libraries yourself.
Required Python libraries/add-ons:

• pywin32-ctypes
• python-tds
• pywin32
• glob2
• gzip-reader
• regex
• pyodbc

If a valid RED installation can not be found

If you have Red 8.5.1.x or higher installed but the script (Setup_Enablement_Pack.ps1) fails to find it on your system then you are most likely running the PowerShell (x86) version which does not show installed 64-bit apps by default. Please open a 64-bit version of PowerShell instead and re-run the script.