Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

In this article

...

You can use this account type to connect Snowflake Snaps with data sources that use Snowflake Azure Database account. 

Info

You can use the Snowflake Azure Account type to create both standard and dynamic accounts. If you want to enter a dynamic value for a specific field, click the Expression Image Modified icon adjacent to the field, and use expressions in the field to specify dynamic values as required.

Prerequisites

None.

Limitations and Known Issues

...

Field NameField TypeDescription
Label*String

Specify a unique label for the account.

Default value: None
Example: Snowflake Azure Account

JDBC JARs

Use this field set to add a list of JDBC jar files to be loaded (Snowflake JDBC jar 3.0.0 or higher). Click  to add a JDBC driver. Add each jar file in a separate row.

JDBC Driver*String

Specify the fully-qualified name of the JDBC driver class to be used for connecting to the server.

Default value: [None]
Example: net.snowflake.client.jdbc.SnowflakeDriver

Hostname*String/Expression

Specify the hostname of the Snowflake server to which you want to connect the new account.

Default value: None
Example: demo.snowflake.net

Port Number*Integer/Expression

Specify the port number associated with the Snowflake database server that you want to use for this account.

Default value: 443 

Username*String/Expression

Specify the username that you want to use to connect to the database server.

Default value: None
Example: testuser

Password*String/Expression

Specify the password associated with the username specified above. This will be used as the default password while retrieving connections.

Default value: None
Example: P@##20!(*67

Database name*String/Expression

Specify the name of the database to which you want to connect.

Default value: None
Example: testdb

Warehouse name*String/Expression

Specify the name of the warehouse to which you want to connect.

Default value: None
Example: testwh

JDBC Driver ClassString

Specify the JDBC driver class to be used to use.

Default Valuenet.snowflake.client.jdbc.SnowflakeDriver
Examplenet.snowflake.client.jdbc.SnowflakeDriver

Azure storage account nameString/Expression

Specify the name of the instance of the Azure storage account.

Default value: None
Example: testazurestorage

Azure storage account keyString/Expression

Specify the key to connect to the instance of the Azure storage account listed above.

You can use either of the two keys available in the Access Key tab of the dashboard in the Azure portal to populate this value.

Default value: None

ContainerString/Expression

Specify the name of the Azure storage blob container that you want to use for hosting files.

Default value: None
Example: Container1

PathString/Expression

Specify the location of the folder in the container listed above where you want to host files.

Default value: None
Example: Folder1/SubFolder1

Shared Access Signature (SAS) Token MethodDropdown list

Specify the method of supplying the SAS token to the Snaps. You can choose between the following two options:

  • User Supplied: Choose this option if you intend to manually enter the shared access token signature.

    If you opt for the User Supplied option, then you need to ensure that your tokens are valid whenever the pipeline is run; else, the pipelines will fail. For more information, see Generating a SAS Token in Snowflake documentation.

  • System Generated: Choose this option if you want Snaps to generate and use the SAS tokens as and when required.

Default value: User Supplied

User tokenString/Expression

Specify the shared access token that you want to use to access the Azure storage blob folder specified in the Path above. You can get a valid SAS token from the Azure portal.

This property is applicable only when you choose User Supplied in the Shared Access Token Signature Method field above. 

Default value: None.

Client side encryptionDropdown list

Select one of the following options to encrypt the blob before uploading to Microsoft Azure. You can choose one of the following two options:

  • None: Indicates that you do not want to use client-side encryption.
  • Custom_Key: Indicates that you want to use a custom key to access the storage blob.

Default value: None
Example: Custom_Key

Custom keyString/Expression

Specify the custom key that you want to use to access the Azure storage blob. This property is applicable only when you select Custom_Key in the Client side encryption field above. The key should be a 128- or 256-bit Base64-encoded key.

Default value: None

URL Properties

Use this field set to configure the URLs associated with this account. It consists of the following fields:

  • URL property name
  • URL property value
Note
titleGranting roles

You can grant roles to the SnapLogic Snowflake account by using the role parameter in the URL Properties field set. Ensure that the roles are predefined in your Snowflake account before configuring the SnapLogic Snowflake account. 

URL Property Name: role

URL Property Value: SYSADMIN

See Roles and Grant Roles for details.


URL property nameString

Specify the name of the URL property.

Default value: None
ExamplequeryTimeout

URL property valueString

Specify the URL property value associated with the URL property name.

Default value: None
Example: 0

Batch size*Integer/Expression

Specify the number of statements that you want to execute at a time.

Note

Select queries are not batched.


Warning

Using a large batch size could use up the JDBC placeholder limit of 2100.

Default value: 50

Fetch size*Integer/Expression

Specify the number of rows you want a query to fetch during each execution.

Warning

Large values could cause the server to run out of memory.


Min pool size*Integer/Expression

Specify the minimum number of idle connections that you want the pool to maintain at a time. 

Default value: 3
Example: 2

Minimum value: 0
Maximum value: No limit

Max pool size*Integer/Expression

Specify the maximum number of connections that you want the pool to maintain at a time.

Note

Snowflake Bulk Load/Bulk Upsert/S3 Upsert Snap requires a minimum of 2 connections per Snap in a pipeline. For example, if a pipeline has a Snowflake Bulk Load Snap and an S3 Upsert Snap, then the pool size must be greater than or equal to 4 for successful execution.

Default value: 50
Example: 40

Minimum value: 0
Maximum value: No limit

Max life time*Integer/Expression

Specify the maximum lifetime of a connection in the pool. Ensure that the value you enter is a few seconds shorter than any database or infrastructure-imposed connection time limit. A value of 0 indicates an infinite lifetime, subject to the Idle Timeout value. An in-use connection is never retired. Connections are removed only after they are closed.

Default value: 60
Example: 50

Idle Timeout*Integer/Expression

Specify the maximum amount of time a connection is allowed to sit idle in the pool. A value of 0 indicates that idle connections are never removed from the pool.

Default value: 5
Example: 4

Checkout timeout*Integer/Expression

Specify the number of milliseconds you want the system to wait for a connection to become available when the pool is exhausted. A value of 0 instructs the system to wait forever. For any other value, the system throws an exception after the wait time has expired.

Default value: 10000
Example: 9000

...