Snowflake

A cloud-based data platform offers a scalable, secure, and high-performance relational database that offers online services and minimal management.

Supported Methods

Means for Lumi to connect to the client to implement the services required

• Direct

  The default / typical connection option. Interfaces directly with the target system over the Internet with no mediation. Suitable for most cloud-hosted scenarios or public-facing resources. See Network Configuration for more details.

• Gateway An alternative connection method leveraging a Lumi AI Data Gateway. This uses Lumi AI's purpose-built connection agent to mediate communications. Ideal for restricting access to systems within a protected network. For more information, see Data Gateway.

Supported Limits

The following are limitations that can be set to fine tune the agents' actions:

• Cost Limit Before running a query, if the system supports it, the system-specific compute cost (or surrogate) estimate will be processed and compared to an organization-level/admin-set cost limit for systems of this type (if configured/set). If exceeded, the query will not run (and either the workflow will attempt an optimization or the user will be notified).

• Duration Limit An alternative to cost, queries will be stopped the system supports a duration/timeout limit and one is set/configured at the organization level (across systems).

Available Parameters

These properties are the essential source system connection properties that all queries are directed towards.

* Required parameters

Note: The Gateway parameter is common to all systems (when supported) and is only available when gateway is the selected connection method.

Account Identifier*

Provide the Snowflake unique account identifier within your organization.

Snowflake Account Identifier Documentation

Username*

Username of the generated database user which will be used for interactions and transactions.

Special Considerations

• If double quotes are used, then the name will be case sensitive

• Encasing a username with [ ] allows for a usage of reserved words and the @ character

• Username can include alphanumeric characters, hyphens (-), underscores (_), and periods (.)

👍 Valid Examples

• Uses alphanumeric characters : lumi1

• Utilizing underscore (_) in place of spaces: user_number

👎 Invalid Examples

• Starting with a number: 1lumi

• Utilizing spaces: user name

• Using invalid characters: user#1

Password

Password of the generated database user which will be used for interactions and transactions (if using password-based authentication).

Private key

Private key of the generated database user which will be used for interactions and transactions (if using Public / Private Key Pair-based authentication)

Database*

Literal database name that will be used for transactions within the agents.

👍 Valid Examples

• Uses alphanumeric characters: lumi1

• Utilizing underscore (_) in place of spaces: new_database

👎 Invalid Examples

• Starting with a number: 1lumi

• Utilizing spaces: user name

• Using reserved words unquoted: select

Warehouse*

Literal warehouse name that will be used for transactions within the agents.

How To Generate A Warehouse

👍 Valid Examples

• Uses alphanumeric characters: lumi1

• Utilizing underscore (_) in place of spaces: new_database

👎 Invalid Examples

• Starting with a number: 1lumi

• Utilizing spaces: user name

• Using reserved words unquoted: select

Role*

The role associated with the an account to provide access and permissions.

How To Generate A Role

System Permissions & Configuration

Provided user must have the following:

• If applicable generate a new User with:

  • DEFAULT_ROLE, DEFAULT_WAREHOUSE, DEFAULT_NAMESPACE, and PASSWORD

• Generate a new ROLE and grant privileges:

  • GRANT USAGE ON DATABASE <database> TO ROLE <role>

  • GRANT USAGE ON SCHEMA <database.schema> TO ROLE <role>

• Grant SELECT to all tables via GRANT SELECT ON ALL TABLES IN SCHEMA <database.schema> TO ROLE <role>

• When applicable, grant the role to the generated user

For configurations:

• Ensure the server is allowing connections from the Lumi gateway or server via the firewall

Special Notes

• If case sensitivity is required and other special characters, utilize double quotes for database name; ex. "New_database"

Common Issues

• Ensure the firewall settings allow for a connection to the database

• Ensure the username, password, and database values are explicitly provided