This page will walk you through the setup of Snowflake in K.
Step 1) Establish Snowflake Access
Create a Snowflake user with access to following tables in the Snowflake database.
account_usage.history
account_usage.views
account_usage.tables
account_usage.columns
account_usage.copy_history
account_usage.grants_to_roles
account_usage.grants_to_users
Snowflake integration uses username/password. Using keys will be supported in an upcoming release
Step 2) Connecting K to Snowflake
Select Platform Settings in the side bar
In the pop-out side panel, under Integrations click on Sources
Click Add Source and select Snowflake
Select Direct Connect and add your Snowflake details and click Next
Name: The name you wish to give your Snowflake DB in K
Host: Add the host URL of your Snowflake account.
Omit the https:// and anything from and including .snowflakecomputing.com/….
For example:
Add the user details and click Save and Next
Select the Databases you wish to load into K and click Finish Setup
Return to the Sources page and locate the new Snowflake source that you loaded
Click on the clock icon to select Edit Schedule and set your preferred schedule for the Snowflake load
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 Snowflake setup
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
Select Snowflake and click Run
After the source is triggered, the screen will change to the Monitor tab where you can see the progress of the job.
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
Troubleshooting failed loads
If the job failed at the extraction step
Check the error. Contact KADA Support if required.
Rerun the source job
If the job failed at the load step, the landing folder failed directory will contain the file with issues.
Find the bad record and fix the file
Rerun the source job