Required Information for Snowflake Connection

When adding a connection, you are prompted for specific information for the connection type. Gather the following information before adding the connection.

Important: Beginning September 30, 2024, Snowflake is deprecating username/password authentication for new accounts in favor of key-pair authentication. To temporarily opt out of this authentication change for new accounts and allow service users to continue using password authentication, mark the service users as legacy service users in Snowflake:ALTER USER <service-user> SET TYPE = LEGACY_SERVICE;. See the Snowflake documentation for more details.

Required Information

The user account used to connect to Tamr should not be used for any other purpose.

The following parameters are case-sensitive.

• Username
  This user's default Snowflake role is used when connecting to Snowflake. The default role should be set to one that's appropriate for Tamr only and has permissions to access the necessary tables in Snowflake.
• Private Key or Password
  This user's credentials for authenticating with Snowflake. Key-pair authentication is preferred over password-based, because the latter is scheduled for deprecation by Snowflake.
• Organization Name
• Account Name
  This is the Account Identifier in Snowflake. The full account identifier must be specified, which is usually part of your Snowflake URL: <account_identifier>
  See Snowflake documentation on Account Identifiers for more information.
• Database
• Schema
• Warehouse

You can import Snowflake views as source datasets. You need permissions to the view to do this. See the Snowflake documentation for more detail. When adding your source, enter the name of your view in the Table field.

Important Known Issue for Snowflake Connections:

Do not use the DEFAULT warehouse for Snowflake Source connections.

Important Note for Numeric Values in Snowflake Sources

Snowflake treats all numeric values as 128-bit integers (Int128). Tamr Cloud supports up to 64-bit integers (Int64), and automatically converts numeric values to Int64. If your data includes numeric values over Int64 and you need to preserve precision above Int64, covert these values to strings in your upstream systems before loading the data into Tamr Cloud.

Important Note for Vector Types in Snowflake Sources

Tamr does not currently support loading views or tables if one of the columns is a Vector Type.