Snowflake
Visier can retrieve data through this connector if the following requirements are met.
Overview
Visier offers two Snowflake connectors.
- Snowflake (Beta): Applies Visier's next generation data onboarding architecture to Snowflake, including an easy-to-use wizard to navigate and select tables directly from Snowflake. Mirrors your Snowflake data storage and uses Apache Spark to reduce onboarding time, simplify connector configuration, and load data changes more efficiently. This connector supports Snowflake tables and does not support Snowflake views. For more information, see Snowflake (Beta) requirements.
- Snowflake (Legacy): Uses Visier's original data-in connector architecture. For more information, see Snowflake (Legacy) requirements.
Snowflake (Beta) requirements
Prerequisites
- Create an integration user in Snowflake.
- Enable Snowflake (Beta) and table sources. For more information, contact your Customer/Partner Success Manager.
- If your Snowflake instance is hosted on AWS, instruct Visier to add your S3 bucket to Visier's VPC policy.
- Allow network and data traffic between Visier and your source system. For more information, see Allow Visier Connections.
Integration user
Create an integration user in your source system and assign it the appropriate security access so that Visier can retrieve your source data through this user.
|
Access |
Description |
|---|---|
|
SELECT or OWNERSHIP access |
|
Connector credentials
Create a connector credential in Visier to authenticate and authorize access to your source system. Connector credentials can be created in Studio or through an API. For more information, see Set Up Data Connectors and "Create a connector credential" in API Reference. You will need to provide the following credentials in your connector credential configuration.
Note: We only support key-pair authentication because Snowflake blocks sign-ins using single-factor authentication with passwords as of November 2025. For instructions on how to configure key-pair authentication, see Key-pair authentication and key-pair rotation.
|
Credential |
Description |
Example |
|---|---|---|
|
Account Identifier |
The unique identifier of the account to retrieve data from. |
SAMPLE-ACCOUNT-IDENTIFIER |
|
Warehouse |
The warehouse to use. |
SAMPLEWAREHOUSE |
|
Username |
The integration user’s username. |
IntegrationUser |
|
Private Key |
The generated private key. |
-----BEGIN PRIVATE KEY----- ... ----END PRIVATE KEY---- |
|
Database (Optional) |
The database to retrieve data from. Useful if you want to restrict access to a specific set of tables in a particular database. |
SNOWFLAKE_SAMPLE_DATA |
|
Schema (Optional) |
The schema associated with the database. Useful if you want to restrict access to a specific set of tables in a particular schema. |
TPCH_SF1 |
|
Key Passphrase (Optional) |
The passphrase for the encrypted private key. |
|
|
Role (Optional) |
The database role that provides access to securable objects. |
|
How the connector loads data
Initially, data connectors retrieve a full history for each subject to generate an initial history of events. In each subsequent data retrieval, each connector handles the data load differently.
- Full load: All data from the source system is loaded into Visier.
- Delta load: Only changed data is loaded into Visier. A delta load may take either the entire history or a specific number of years of history for each changed record.
- Snapshot load: All data at a particular point in time. A snapshot load does not contain historical records or show changes over time.
- Partial load: A subset of data is loaded into Visier.
After the initial load, this connector does one of:
- Full load: If table change tracking is not enabled, the connector retrieves all data from Snowflake every time.
- Delta load: To support delta loads, enable change tracking in Snowflake for each table you want to load in Visier. If the time between data extractions exceeds the data retention period, a full load occurs. The default data retention period in Snowflake is 1 day.
Sync data
After the connector credential is created, you can configure the connector to bring data into Visier. For more information, see Sync Snowflake Data.
Snowflake (Legacy) requirements
Prerequisites: Create an integration user in Snowflake.
Integration user
Create an integration user in your source system and assign it the appropriate security access so that Visier can retrieve your source data through this user.
|
Access |
Description |
|---|---|
|
SELECT or OWNERSHIP access |
|
Connector credentials
Create a connector credential in Visier to authenticate and authorize access to your source system. Connector credentials can be created in Studio or through an API. For more information, see Set Up Data Connectors and "Create a connector credential" in API Reference. You will need to provide the following credentials in your connector credential configuration.
Note: We recommend using key-pair authentication because Snowflake will block sign-ins using single-factor authentication with passwords by November 2025. For instructions on how to configure key-pair authentication, see Key-pair authentication and key-pair rotation.
|
Credential |
Description |
Example |
|---|---|---|
|
Account Identifier |
The unique identifier of the account to retrieve data from. |
SAMPLE-ACCOUNT-IDENTIFIER |
|
Warehouse |
The warehouse to use. |
SAMPLEWAREHOUSE |
|
Username |
The integration user’s username. |
IntegrationUser |
|
Private Key |
The generated private key. |
-----BEGIN PRIVATE KEY----- ... ----END PRIVATE KEY---- |
|
Database (Optional) |
The database to retrieve data from. Useful if you want to restrict access to a specific set of tables in a particular database. |
SNOWFLAKE_SAMPLE_DATA |
|
Schema (Optional) |
The schema associated with the database. Useful if you want to restrict access to a specific set of tables in a particular schema. |
TPCH_SF1 |
|
Key Passphrase (Optional) |
The passphrase for the encrypted private key. |
|
|
Role (Optional) |
The database role that provides access to securable objects. |
|
Data files
The Snowflake data connector only retrieves data stored in Snowflake for use in Visier.
For other data, you must provide that data through alternative methods such as SFTP or Visier’s other data connectors. For more information about sending data to Visier, see File Upload.
How the connector loads data
Initially, data connectors retrieve a full history for each subject to generate an initial history of events. In each subsequent data retrieval, each connector handles the data load differently.
- Full load: All data from the source system is loaded into Visier.
- Delta load: Only changed data is loaded into Visier. A delta load may take either the entire history or a specific number of years of history for each changed record.
- Snapshot load: All data at a particular point in time. A snapshot load does not contain historical records or show changes over time.
- Partial load: A subset of data is loaded into Visier.
After the initial load, this connector only retrieves data for changed records.