Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Scroll ignore
scroll-viewporttrue
scroll-pdftrue
scroll-officetrue
scroll-chmtrue
scroll-docbooktrue
scroll-eclipsehelptrue
scroll-htmltrue
scroll-epubtrue

Open in new tab

This page will walk guide you through the setup of Snowflake Redshift in K using the direct connect method.

Integration details

Scope

Included

Comments

Metadata

Status
colourGreen
titleYES

 

Lineage

Status
colourGreen
titleYES

 

Usage

Status
colourGreen
titleYES

Sensitive Data Scanner

Status
colourGreen
titleYES

 

...

Step 1) Establish Redshift Access

Info

The kada user MUST be either (one or the other)

Create a kada user with either (one or the other)There are 2 methods for providing K access to Redshift: Super user or Custom user.

Super user method: Create a new Superuser - refer to https://docs.aws.amazon.com/redshift/latest/dg/r_superusers.html to view all required data.

...

Custom user methods: Create a user with

  1. Unrestricted SYSLOG ACCESS - refer to https://docs.aws.amazon.com/redshift/latest/dg/c_visibility-of-data.html. This will allow full access to the STL tables for the user.

    Code Block
    languagesql
    ALTER USER <kada user> SYSLOG ACCESS UNRESTRICTED; -- GRANTS READ ACCESS

  2. Select Access to existing and future tables in all Schemas for each Database you want K to ingest.

    1. List all existing Schema in the Database by running

      Code Block
      languagesql
      SELECT DISTINCT schema_name FROM svv_all_tables; -- LIST ALL SCHEMAS

    2. For each schema above do the following to allow the kada user select access to all tables inside the Schema and any new tables created in the schema thereafter.

      You also must do this for ANY new schemas created in the Database to ensure K has view of it.

      Code Block
      languagesql
      GRANT USAGE ON SCHEMA <schema name> TO <kada user>;
      GRANT SELECT ON ALL TABLES IN SCHEMA <schema name> TO <kada user>;
      ALTER DEFAULT PRIVILEGES IN SCHEMA <schema name> GRANT SELECT ON TABLES TO <kada user>;

  3. The PG tables are granted per database but generally all users should have access to them on DB creation. In the event the user doesn’t have access, explicit grants will need to be done per new DB in Redshift.

Code Block
languagesql
GRANT USAGE ON SCHEMA pg_catalog TO <kada user>;
GRANT SELECT ON ALL TABLES IN SCHEMA pg_catalog TO <kada user>;

...

Info

Note that scheduling a source can take up to 15 minutes to propagate the change.

...

Step 3) Manually run an ad hoc load to test

...

  • Select Platform Settings in the side bar

  • In the pop-out side panel, under Platform Settings click on Batch Manager

  • In Source Load click Run

...

Redshift setup

  • Next to your new Source, click on the Run manual load icon

    Image Added
  • Confirm how your want the source to be loaded

    Image Added
  • After the source load is triggered, the screen will change a pop up bar will appear taking you to the Monitor tab where you can see in the Batch Manager page. This is the usual page you visit to view the progress of the job.

...

  • source loads

    Image Added

Info

A manual source load will also require a manual run of

  • DAILY

  • GATHER_METRICS_AND_STATS

To load all metrics and indexes with the manually loaded metadata. These can be found in the Batch Manager page

...