Overview
The Jitterbit Harmony Snowflake Connector is accessed from the Connectivity tab of the design component
palette:

This connector is used to first configure a Snowflake connection, establishing access to
an account on the Snowflake server, and then used to configure one or more Snowflake activities
associated with that connection as either a source or target within an operation:
-
Query Activity: Retrieves an existing record on a Snowflake connection and is intended
to be used as a source in an operation.
-
Get Activity: Retrieves table or view data from a Snowflake connection and is intended to
be used as a source in an operation.
-
Put Activity: Puts data into a table (either as a CSV file or directly mapped to columns
of a table) on a Snowflake connection and is intended to be used as a target in an operation.
-
Invoke Stored Procedure Activity: Provides the ability to use stored
procedures created in Snowflake and is intended to be used as a target in an operation.
-
Delete Activity: Deletes table data on a Snowflake connection and and is intended to be
used as a target in an operation.
The Snowflake connector uses the Snowflake JDBC Driver
and the Snowflake SQL commands. Only
Comparison Operators are supported
in this version in the query activity. For additional information on the Snowflake Query activity, see the
Snowflake documentation.
The Snowflake connector is restricted to using CSV files as input and output for its activities. The Snowflake
connector requires the use of an agent version 10.1 or later.
Together, a specific Snowflake connection and its activities are referred to as a Snowflake endpoint.
Once a connection is configured, activities associated with the endpoint are available from the Endpoints
filter:

Known Issue
- Snowflake: Database and table names converted to uppercase
- Summary: By default, database and table names are converted to uppercase when used by Snowflake.
- Additional Info: Converted database and table names may not match their source names and generate an error.
- Workaround: Use double quotes around a database or table name instead of single quotes to preserve the desired case.