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:

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:

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.
    1In Administrator, select Connections.
    2Click New Connection.
    3Enter the following connection details:
    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
    Snowflake Data Cloud
    4In the Snowflake Data Cloud Properties section, select the runtime environment where you want to run the tasks. The runtime environment is either a Secure Agent or a serverless runtime environment.
    5In the Connection section, select the authentication method.
    You can use the following authentication methods to connect to Snowflake:

Standard authentication

This authentication method requires the Snowflake account user name and password credentials to connect to Snowflake.
The following table describes the basic connection properties for standard authentication:
Property
Description
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. If the account name contains underscores, you need to use the alias name. To use an alias name, contact Snowflake Customer Support.
Warehouse
The Snowflake warehouse name.
Property
Description
Role
The Snowflake role assigned to the user.
Additional JDBC URL Parameters
The additional JDBC connection parameters.
You can specify multiple JDBC connection parameters, separated by ampersand (&), in the following format:
<param1>=<value>&<param2>=<value>&<param3>=<value>....
For example, you can pass the following database and schema values when you connect to Snowflake:
db=mydb&schema=public
When you add parameters, ensure that there is no space before and after the equal sign (=).

Key pair authentication

This authentication method requires the private key file and private key file password, along with the existing Snowflake account user name to connect to Snowflake.
The following table describes the basic connection properties for key pair authentication:
Property
Description
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. If the account name contains underscores, you need to use the alias name. To use an alias name, contact Snowflake Customer Support.
Warehouse
The Snowflake warehouse name.
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 in the Secure Agent machine:
  • - On Windows: C:\Users\path_to_key_file\rsa_key.p8
  • - On Linux: /export/home/user/path_to_key_file/rsa_key.p8
To use the serverless runtime environment, specify the following path and key file name in the serverless agent directory:
/home/cldagnt/SystemAgent/serverless/configurations/ssl_store/<Private key file name>
Note: Verify that the keystore is FIPS-certified.
The following table describes the advanced connection properties for key pair authentication:
Property
Description
Additional JDBC URL Parameters
The additional JDBC connection parameters.
You can specify multiple JDBC connection parameters, separated by ampersand (&), in the following format:
<param1>=<value>&<param2>=<value>&<param3>=<value>....
For example, you can pass the following database and schema values when you connect to Snowflake:
db=mydb&schema=public
When you add parameters, ensure that there is no space before and after the equal sign (=).
Private Key File Password
Password for the private key file.