Snowflake setup
Last updated
Last updated
The Snowflake connector enables you to quickly establish a connection with your Snowflake warehouse to load data and seamlessly run transformation models.
In this guide, you'll learn how to:
Prepare a sample dataset in Snowflake
Set up a connection from Recurve to Snowflake
You already join a Recurve organization.
You have a Snowflake account. If you don’t have one, sign up for a free trial here: .
To demonstrate the connetion process, we'll be using the jaffle_shop dataset — a fictional e-commerce store's data provided by the dbt community. This dataset offers a practical example of typical e-commerce data structures that mirror real-world scenarios.
You can use the CLI tool generate synthetic data for any specified year range.
The dataset includes these tables:
Customers (who place Orders)
Orders (from those Customers)
Products (the food and beverages the Orders contain)
Order Items (of those Products)
Supplies (needed for making those Products)
Stores (where the Orders are placed and fulfilled)
Tweets (Customers sometimes issue Tweets after placing an Order)
Or simply download the generated data below:
With the sample data prepared in the CSV files, we can use the Snowflake web interface to load them into your database.
Follow these steps:
From the homepage, click Upload local files to open the data loading wizard:
Click Browse, and select a CSV file from the prepared dataset.
Click + Database to create a dedicated database for our use case.
Here we can name it RECURVE_DEMO.
Select + Create new table from the dropdown and enter the corresponding table name. For example, for raw_customers.csv, name the table raw_customers.
Click Next.
At this step, Snowflake automatically detects table schema and presents it in the interface. You can verify if the columns' names and data types are correctly detected and adjust accordingly. For our sample CSV files, make sure that the first row is considered the header, containing column names.
Click Load to confirm and wait for the loading process to complete.
Repeat step 2 to load all the tables into the same database.
Go to your .
