Documentation

Connecting to Snowflake

Abstract

SummaryHow to specify your Snowflake warehouse information so that Alooma can connect. Enter the required information and then grant access to Snowflake by running the commands provided.

Follow the instructions below to configure a Snowflake output and grant access to Snowflake.

  1. Click on the Output node of the Plumbing page.

  2. If not selected, choose the Settings tab.

  3. Fill out the connection information:

    • Please note that all fields are case sensitive

    • Account subdomain (the subdomain portion of "http://<subdomain>.snowflakecomputing.com", NOT the entire URL)

      Note

      For Snowflake on Azure, the value to enter for the Account subdomain will look something like this: alooma_partner.east-us-2.azure

    • Warehouse (case sensitive)

    • Username (case sensitive)

    • Password

    • Database name (case sensitive)

      Note

      Snowflake is case-sensitive, so make sure to use uppercase letters UNLESS you know for sure the database name includes lowercase letters. If it does include lowercase letters, wrap the database name in quotes: "database_name"

    • Default schema (case sensitive - this is the one we'll write to by default, though you'll be able to choose to map to any other schema we have access to).

  4. If you'd like to use Snowpipe to load your data, mark the Load continuously using Snowpipe checkbox.

    Snowpipe is Snowflake's delivery mechanism which uses authenticated REST calls in order to load data asynchronously. Snowpipe uses Snowflake-supplied compute resources in order to load the files. This can lead to cost savings as you are billed for the Snowpipe warehouse usage at per-second granularity without a per-minute activation minimum. The result is that there's no more cost overhead to loading data in real time, and you won't have to wait for batch loads to access data.

    Generally we recommend enabling Snowpipe unless your Snowflake instance is constantly active.

    Note

    If you are editing an existing Snowflake output to enable Snowpipe, you will need to update your Snowflake user with the generated public key. To do this, mark the Load continuously using Snowpipe box, then copy and run the SQL code block in the grey box.

  5. Specify a merge (replication update) frequency. You can choose the default or enter your own cron string. If you have existing merges, you can also mark the box to have the new schedule applied to them as well.Schedule Syntax

  6. At this point, you're ready to grant Snowflake access by running the code displayed in the grey box. 

    To run the code, you'll first need to log in to your Snowflake account and open up an SQL worksheet, or connect to Snowflake using your SQL console of choice. 

    Note

    You can choose not to validate the Snowflake settings and save them regardless of their validity by checking the "do not validate" option (not recommended).

  7. Once you've run the code, you are all set. Click Save changes.

Alooma connects to Snowflake over SSL by default.

That's it! You've created a Snowflake output. Alooma can now connect to your target Snowflake data warehouse.

What's next? Here's a quick video showing how to set up an input.

Search results

    No results found