Page History
...
Table of Contents maxLevel 2 minLevel 2
Prerequisites For PostgreSQL Metadata
Before you begin the following prerequisites must be met:
...
- RED supports the following versions for the metadata repository: PostgreSQL 12 or higher
Prerequisites Target Database
Before you begin the following prerequisites must be met:
- Access to an Azure SQL Server/SQL Server (Target Environment), with the following connectivity information:
- Server Name
- Database Name
- User Name
- Password
- At least one schema available to use as a RED Data Warehouse Target
- Azure SQL Server software installed
- Azure SQL Server ODBC driver (64-bit)
- Add ODBC DSN for Azure SQL Server Target Database
- Azure SQL Server ODBC driver (64-bit)
- SQL Server software installed
- SQL Server ODBC driver (64-bit)
- Add ODBC DSN for SQL Server Target Database
- SQL Server ODBC driver (64-bit)
- Python 3.8 or higher
- Select "Add Python 3.8 to PATH" from the installation Window
- Pip Manager Install with the command:
python -m pip install --upgrade pip
Enablement Pack Setup Scripts
The Enablement Pack Install process is entirely driven by scripts. The below table 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. For Example > .\Setup_Enablement_Pack.ps1 -help
Step-By-Step Guide
Setup and configure RED Metadata Repository
Run Powershell as Administrator:
...
Info | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
If RED repository exists, it will prompt to upgrade the repository. This enablement pack will overwrite any existing Source Enablement Pack UI Configs:
To ensure existing Source Enablement Pack connections and associated Load Tables continue to browse and load: |
Info |
---|
A change to the script exit code has been introduced. Whenever a load/update script is regenerated, it is essential to regenerate the linked action script. Similarly, regenerating the action scripts requires regenerating the associated load/update scripts to keep both scripts in sync. |
Install or Update WhereScape Python Modules
Run Script As Administrator
...
There are two steps in this script:
1. Install 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
...
Note : Skip this step for new installations.
Set Connection defaults for a Template Set (For Existing Installations)
Code Block |
---|
Script 4 > . .\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:
The below two are common for SQL Server and Azure SQL
...
NOTE: For Blob extended properties refer to the below section
Configure Azure SQL Database and Blob Storage
Run the below queries in Azure SQL database query editor.
CREATE MASTER KEY ENCRYPTION BY PASSWORD = '<MASTER_KEY>';
CREATE DATABASE SCOPED CREDENTIAL <BlobStorageCredential> WITH IDENTITY = 'SHARED ACCESS SIGNATURE', SECRET = '<SAS_TOKEN>';
DROP EXTERNAL DATA SOURCE <Blob Data Source>;
CREATE EXTERNAL DATA SOURCE <Blob Data Source>WITH (TYPE = BLOB_STORAGE,LOCATION = 'https://<Blob Storage Account>.blob.core.windows.net/<Blob Storage Container>/<Directory>',CREDENTIAL = <BlobStorageCredential> );
NOTE: Keywords mentioned in <> in blue need to be replaced with the values that can be found on Azure
Source Enablement Pack Support
Source Pack Name | Supported By Azure SQL Server/SQL Server | Supported Features | Prerequisites |
Cloud File Parser
|
| Bulk load | Refer to Windows Parser Guide |
Windows Parser |
| Load Template, Source Properties will have the option to select parser type to load the files. | Refer to Windows Parser Guide |
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 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
Note |
---|
In the event, you can not bypass the Powershell execution policy due to group policies you can instead try "-ExecutionPolicy RemoteSigned" which should allow unsigned local scripts. |
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 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 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
Tip |
---|
To avoid having to provide all the parameters again you can copy the full command line with parameters from the first "INFO" message from the beginning of the console output. |
Bulk load error on SQL SERVER
Interactive load
Scheduler load
For bulk load errors, the 'bulkadmin' permission is required.
SQL SERVER > SECURITY > LOGINS > USER > PROPERTIES >SERVER ROLES
For bulk load error Operating system error code 5(Access is denied)
Code Block |
---|
Failed to load data: ('42000', '\[42000\] \[Microsoft\]\[ODBC Driver 17 for SQL Server\]\[SQL Server\]Cannot bulk load because the file "C:\WhereScape\Temp\...\xxxx.csv" could not be opened. Operating system error code 5(Access is denied.). (4861) (SQLExecDirectW)') |
- Grant SQL Server access to the bulk load folder by adjusting folder permissions. Navigate to the folder, right-click, select "Properties," go to the "Security" tab, click "Edit," then "Add." In the new window, select "Advanced," click "Find Now," and locate the appropriate SQL Server user (e.g., SQLServerMSSQLUser$UserName$SQLExpress). Confirm by clicking "OK" through all opened dialogs.
- If the first fix doesn't resolve the issue, verify if permissions are applied to subfolders as well. Navigate to the advanced settings, and check the 'Inheritance' status. If it's 'Disabled,' enable it by using the "Allow Inheritance" button.
Row Terminator For Linux
Error Message
Code Block |
---|
Failed to load data: ('42000', '[42000] [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Cannot obtain the required interface ("IID_IColumnsInfo") from OLE DB provider "BULK" for linked server "(null)". (7301) (SQLExecDirectW)') |
- pywin32-ctypes
- python-tds
- pywin32
- glob2
- gzip-reader
- regex
- pyodbc
If a valid RED installation can not be found
If you have RED 10.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.
...