DataLane Snowflake Integration Setup Guide

Last updated: April 27, 2026

Questions? Contact [email protected]

This document is your complete guide for connecting Snowflake to DataLane as a Source. It covers both the Snowflake share setup and the final setup in the DataLane UI.

1 What is the DataLane Snowflake Integration

1.1 What DataLane Does in Snowflake

DataLane connects to your Snowflake account using a dedicated service user with RSA key-pair authentication. DataLane uses that connection to read source data, discover table metadata, and support downstream workflows such as schema creation, matching, enrichment, and exports.

What DataLane does:

  • Reads Snowflake databases, schemas, tables, and columns that the DataLane role can access

  • Reads selected Snowflake tables for DataLane workflows

  • Uses a dedicated Snowflake warehouse for queries

  • Writes DataLane-managed output to a dedicated managed database and schema

  • Uses RSA key-pair authentication instead of a Snowflake password

What DataLane does not do:

  • Store a Snowflake password

  • Delete records or tables from your Snowflake account

  • Modify your existing source tables

  • Write into the imported read-only database created from a Snowflake share

  • Require a local agent, VPN, or custom code running in your environment

1.2 How the Setup Works

Most Snowflake setups have two parts:

  • Snowflake share setup — DataLane grants your Snowflake account access to an inbound share, and your team creates an imported database from that share.

  • Snowflake source connection — your team connects Snowflake in DataLane, runs the generated setup SQL, tests the connection, and creates the first DataLane schema.

If your team already has the DataLane Snowflake share configured and can query the imported database in Snowflake, you can skip the share setup section and start at 2.3 Connect Snowflake as a Source in DataLane.

1.3 Who Should Be Involved

Role

Primary responsibility

Where they usually work

Snowflake admin

Inbound share, imported database, Snowflake grants, setup SQL, and least-privilege changes

Snowflake

DataLane workspace admin

Add source, test connection, review discovered tables, and create the first schema

DataLane UI

Security reviewer

Review the generated SQL grants and approve any narrower access model

Snowflake / internal review

1.4 Key Terms and Identifiers

Snowflake uses several account and share identifiers. Do not use account locator and account identifier interchangeably; they are different values used in different setup steps.

Term / value

Used in

What it means / what to enter

Cloud provider / region

Snowflake share setup

The Snowflake cloud and region where DataLane should provision the share

Account locator

Snowflake share setup

The Snowflake value DataLane uses to grant your account access to the share

Account identifier

DataLane source setup

The value entered in DataLane; usually the beginning of your Snowflake URL

Provider account + share name

Snowflake imported database setup

The values used in CREATE DATABASE ... FROM SHARE ...

Imported database

Snowflake queries and DataLane source access

The read-only database your team creates from the DataLane share

Warehouse

Snowflake queries

Compute used to query the imported database and other readable tables

1.5 What Gets Created in Snowflake

The DataLane UI generates a Snowflake setup script after you enter your account identifier. The script creates the following objects.

Object

Purpose

DATALANE_ROLE

Dedicated role used by the DataLane service account

DATALANE_WH

Dedicated Snowflake warehouse used for DataLane queries; auto-suspends after 60 seconds

DATALANE_SERVICE

Service user that authenticates with RSA key-pair authentication

DATALANE_MANAGED.DATALANE_SCHEMA

Managed database and schema for DataLane write-back and managed outputs

Access grants

Grants that allow DATALANE_ROLE to use the warehouse and read the Snowflake data DataLane should access

1.6 Data Access

By running the setup SQL and testing the connection, you grant DataLane access through DATALANE_ROLE. The default generated script grants broad read access across current and future databases, schemas, and tables so DataLane can discover and use the data you select in the UI.

If your security model requires tighter permissions, you can modify the grants before running the SQL. DataLane needs access to the dedicated warehouse, the DataLane-managed schema, and the database and schema that contain the data DataLane should read.

Option

What it grants

When to use it

Default generated script

Read access across current and future databases, schemas, and tables where grants can be applied

Fastest path when your team is comfortable with broad read discovery

Least-privilege variant

Access only to DATALANE_WH, DATALANE_MANAGED.DATALANE_SCHEMA, and the database / schema DataLane should read

Best for teams that require tighter Snowflake permissions

You can revoke access at any time by disabling or dropping DATALANE_SERVICE, revoking DATALANE_ROLE grants, or deleting the Snowflake source connection in DataLane.

2 Installation & Configuration

2.1 Verify Prerequisites

Before starting, confirm:

  • You know whether the DataLane Snowflake share has already been configured

  • A Snowflake admin can create an imported database from a share

  • A Snowflake admin can run the DataLane setup SQL or adapt it to your least-privilege model

  • A DataLane workspace admin can access Setup → Sources and Schemas in the DataLane UI

  • You have the Snowflake account identifier for the DataLane source setup

  • If the share is not already configured, you have the Snowflake cloud provider / region and account locator

2.2 Set Up or Confirm the DataLane Snowflake Share

Skip this section if your team already has the DataLane Snowflake share configured and can query the imported database in Snowflake.

  1. Send the share setup details to your DataLane representative: cloud provider / region and Snowflake account locator.

  2. Wait for DataLane to provision the share and grant your Snowflake account access.

  3. In Snowflake, confirm the inbound share is visible.

  4. Create an imported database from the share using the provider account and share name from DataLane.

  5. Grant access to the Snowflake role that should read the imported database.

  6. Query the imported database with a warehouse to confirm access.

Common Snowflake SQL patterns for this step:

Purpose

SQL pattern

Inspect inbound shares

SHOW SHARES;

Create imported database

CREATE DATABASE <imported_database_name> FROM SHARE <provider_account>.<share_name>;

Grant imported privileges

GRANT IMPORTED PRIVILEGES ON DATABASE <imported_database_name> TO ROLE <role_name>;

Test query access

USE ROLE <role_name>; USE WAREHOUSE <warehouse_name>; SELECT * FROM <imported_database_name>.<schema_name>.<table_name> LIMIT 10;

Important: The imported database is read-only by design. This is expected for Snowflake databases created from shares.

2.3 Connect Snowflake as a Source in DataLane

In the DataLane UI:

  1. Go to Setup → Sources.

  2. Click Add Source.

  3. Select Snowflake.

  4. Enter your Snowflake account identifier.

  5. Click Continue.

  6. Wait for DataLane to show Connection registered and generate the setup script.

The account identifier is usually the beginning of your Snowflake URL, for example companyname-xu12345. This is not the same value as the account locator used for Snowflake share setup.

2.4 Run the DataLane Setup SQL in Snowflake

What success looks like: the DataLane service user, role, warehouse, managed schema, and access grants are created in Snowflake.

In the DataLane UI:

  1. On the Snowflake setup page, click Copy Setup Script.

  2. Open a Snowflake worksheet.

  3. Run the script as ACCOUNTADMIN, or have your Snowflake admin adapt and run it with equivalent privileges.

  4. If using a least-privilege model, modify only the grant section while preserving the DataLane service user, role, warehouse, managed schema, and RSA public key setup.

  5. Return to DataLane after the script completes successfully.

Security note: the generated script uses RSA key-pair authentication. DataLane stores the private key securely and Snowflake stores the matching public key on DATALANE_SERVICE.

2.5 Test the Connection and Confirm Table Discovery

In the DataLane UI:

  1. Return to the Snowflake source setup page.

  2. Click Test Connection.

  3. Wait for the connection test to complete.

  4. Confirm the source status changes to Connected.

  5. Wait for DataLane to run catalog introspection.

  6. Confirm the expected databases, schemas, tables, and columns appear under the source.

  7. If the source is already connected but tables need to be refreshed, use Introspect Schemas from the source management page.

Note: In the current UI, Introspect Schemas covers databases, schemas, tables, and columns.

2.6 Create Your First DataLane Schema

In the DataLane UI:

  1. Go to Schemas.

  2. Click Create Schema.

  3. Select your Snowflake source connection.

  4. Wait for discovered tables to load.

  5. Choose the root / accounts table.

  6. Choose the locations table if your schema uses locations.

  7. Review the join configuration.

  8. Click Create Schema.

If the expected tables do not appear, go back to the Snowflake source page, confirm DATALANE_ROLE can read the correct database and schema, and run introspection again.

2.7 Verify the Installation

After setup is complete, verify:

  • DataLane → Setup → Sources shows the Snowflake source as connected

  • The expected Snowflake databases, schemas, tables, and columns are discovered in DataLane

  • Snowflake contains DATALANE_ROLE, DATALANE_WH, DATALANE_SERVICE, and DATALANE_MANAGED.DATALANE_SCHEMA

  • DATALANE_ROLE can read the imported database or source schemas that DataLane should use

  • A DataLane schema has been created from the connected Snowflake source

3 Troubleshooting

Problem

Likely cause

What to do

We already have the DataLane share configured

Your team can already query the imported database in Snowflake

Skip share setup and start at 2.3 Connect Snowflake as a Source in DataLane

DataLane UI does not accept the account value

You entered the account locator instead of the account identifier

Use the beginning of your Snowflake URL, for example companyname-xu12345

Connection test failed

Setup SQL did not run successfully, required objects are missing, or DATALANE_ROLE lacks access

Confirm DATALANE_SERVICE, DATALANE_ROLE, DATALANE_WH, and grants exist, then retry Test Connection

No tables were discovered

DATALANE_ROLE cannot read the expected database / schema, or introspection has not completed

Confirm grants, then run Introspect Schemas again

Imported database is read-only

Snowflake imported databases created from shares are read-only by design

Query the imported database, but do not expect write access there

Cannot consume the same share again

Snowflake treats a share as consumable once per account

Coordinate with your Snowflake admin and DataLane representative before recreating the imported database

Least-privilege script works but tables are missing

The narrowed grants do not include all schemas or tables DataLane needs

Grant DATALANE_ROLE USAGE on the database/schema and SELECT on the relevant tables, then introspect again

Warehouse cost concern

DATALANE_WH is dedicated compute for DataLane queries

Confirm auto-suspend is enabled and adjust the warehouse size if your Snowflake admin approves

4 Quick Reference

Item

Value

Integration type

Snowflake Source

Primary DataLane UI path

Setup → Sources → Add Source → Snowflake

Account value entered in DataLane

Snowflake account identifier, usually the beginning of the Snowflake URL

Account value used for share setup

Snowflake account locator

Authentication method

RSA key-pair authentication with DATALANE_SERVICE

Dedicated role

DATALANE_ROLE

Dedicated warehouse

DATALANE_WH

Managed output schema

DATALANE_MANAGED.DATALANE_SCHEMA

Post-connection action

Test Connection, then confirm table discovery / run Introspect Schemas

Final setup step

Create a DataLane schema from the connected Snowflake source