Catalog Source Configuration > Snowflake SQL Script > Before you begin

Before you begin

Before you can extract catalog source metadata, get information from the Snowflake database administrator.

Ensure that the following prerequisites are met:

•You have Snowflake SQL Script files saved on the runtime environment from which you want to extract metadata.
•You have access to Snowflake SQL Script.
•You have database source information to connect to the Snowflake database.
•You use the Snowflake Data Cloud connector.
•Verify permissions.

Verify permissions

To extract Snowflake SQL Script metadata, you need account access and permissions to the Snowflake SQL Script catalog source and Snowflake source system.

Verify that you have the following permissions:

•READ permission to access the folder containing scripts
•Permissions for configuring Snowflake connection
•The SELECT permissions on system tables for the Snowflake database user account:

- select on information_schema.EXTERNAL_TABLES
- select on information_schema.FUNCTIONS
- select on information_schema.PIPES
- select on information_schema.PROCEDURES
- select on information_schema.SCHEMATA
- select on information_schema.SEQUENCES
- select on information_schema.STAGES
- select on SNOWFLAKE.ACCOUNT_USAGE.TAGS
- select on SNOWFLAKE.ACCOUNT_USAGE.TAG_REFERENCES

•The SHOW permissions on database objects for the Snowflake database user account:

- show columns
- show primary keys
- show imported keys
- show streams
- show materialized views
- show tasks
- show databases
- show objects

Create a connection

When you configure a connection, you specify the connection properties for the connection. Connection properties enable an agent to connect to data sources.

You can use the following authentication methods to connect to Snowflake:

•Standard. Uses Snowflake account user name and password credentials to connect to Snowflake.
•KeyPair. Uses the private key file and private key file password, along with the existing Snowflake account user name to connect to Snowflake.

For information about configuring a connection, see Connections in the Administrator help system.

Standard authentication

When you set up a Snowflake Data Cloud connection, configure the connection properties.

The following table describes the Snowflake Data Cloud connection properties for the Standard authentication mode:

Property	Description
Connection Name	Name of the connection. Each connection name must be unique within the organization. Connection names can contain alphanumeric characters, spaces, and the following special characters: _ . + -, Maximum length is 255 characters.
Description	Description of the connection. Maximum length is 4000 characters.
Type	The Snowflake Data Cloud connection type.
Runtime Environment	The name of the runtime environment where you want to run the tasks.
Authentication	The authentication method that the connector must use to log in to Snowflake. Select Standard. Default is Standard.
Username	The user name to connect to the Snowflake account.
Password	The password to connect to the Snowflake account.
Account	The name of the Snowflake account. For example, if the Snowflake URL is https://<123abc>.us-east-2.aws.snowflakecomputing.com/console/login#/, your account name is the first segment in the URL before snowflakecomputing.com. Here, 123abc.us-east-2.aws is your account name. If you use the Snowsight URL, for example, https://app.snowflake.com/us-east-2.aws/<123abc>/dashboard, your account name is 123abc.us-east-2.aws Note: Ensure that the account name doesn't contain underscores. To use an alias name, contact Snowflake Customer Support.
Warehouse	The Snowflake warehouse name.
Role	The Snowflake role assigned to the user.
Additional JDBC URL Parameters	The additional JDBC connection parameters. Enter one or more JDBC connection parameters in the following format: <param1>=<value>&<param2>=<value>&<param3>=<value>.... For example, pass the database and schema values when you connect to Snowflake: db=mydb&schema=public Important: Ensure that there is no space before and after the equal sign (=) when you add the parameters.

Key pair authentication

The following table describes the Snowflake Data Cloud connection properties for the KeyPair authentication type connection:

Connection property	Description
Connection Name	Name of the connection. Each connection name must be unique within the organization. Connection names can contain alphanumeric characters, spaces, and the following special characters: _ . + -, Maximum length is 255 characters.
Description	Description of the connection. Maximum length is 4000 characters.
Type	The Snowflake Data Cloud connection type.
Runtime Environment	The name of the runtime environment where you want to run the tasks.
Authentication	The authentication method to log in to Snowflake. Select KeyPair.
Username	The user name to connect to the Snowflake account.
Account	The name of the Snowflake account. For example, if the Snowflake URL is https://<123abc>.us-east-2.aws.snowflakecomputing.com/console/login#/, your account name is the first segment in the URL before snowflakecomputing.com. Here, 123abc.us-east-2.aws is your account name. If you use the Snowsight URL, for example, https://app.snowflake.com/us-east-2.aws/<123abc>/dashboard, your account name is 123abc.us-east-2.aws. Note: Ensure that the account name doesn't contain underscores. To use an alias name, contact Snowflake Customer Support.
Warehouse	The Snowflake warehouse name.
Additional JDBC URL Parameters	The additional JDBC connection parameters. Enter one or more JDBC connection parameters in the following format: <param1>=<value>&<param2>=<value>&<param3>=<value>.... For example, pass the database and schema values when you connect to Snowflake: db=mydb&schema=public Important: Ensure that there is no space before and after the equal sign (=) when you add the parameters.
Private Key File	Path to the private key file, including the private key file name, that the Secure Agent uses to access Snowflake. For example, specify the following path and key file name: - On Windows: C:\Users\path_to_key_file\rsa_key.p8 - On Linux: /export/home/user/path_to_key_file/rsa_key.p8 Note: Verify that the keystore is FIPS-certified.
Private Key Password	Password for the private key file.