Snowflake@1
Snowflake@1 reads data from Snowflake. Nothing to install.
Connects to
Snowflake, in any cloud and region.
Example
- Name
- MySnowflakeDatabase
- Technology
- Snowflake
- Provider
- Snowflake@1
- Connection string
account=testaccount; user=%USER_NAME%; password=%PASSWORD%; db=testdb; schema=testschema;
Data sources:
- Name: MySnowflakeDatabase
Provider: Snowflake@1
Technology: Snowflake
Connection string: >
account=testaccount;
user=%USER_NAME%;
password=%PASSWORD%;
db=testdb;
schema=testschema;
Connection string
A Snowflake connector for .NET connection string — key=value pairs separated by semicolons. The keys you will use most:
| Key | Meaning |
|---|---|
account |
Your account identifier, e.g. myorg-myaccount |
user, password |
Credentials |
db |
Database to connect to |
schema |
Default schema for unqualified names |
warehouse |
Virtual warehouse that runs the statements; the user’s default when omitted |
role |
Role to assume; the user’s default when omitted |
The full list, including other authenticators, is in the Snowflake connector for .NET documentation.
A password, or the whole string, can come from an environment variable — %NAME% is replaced with the value of NAME; see How every provider is used.
Settings
None beyond Connection string.
Query
One SQL statement in Snowflake’s dialect that returns a result set.
Prerequisites
None. The driver ships with CAT. Windows; on Linux it has no extra dependencies and is expected to work, but it has not been tested there.
Serving test and data source definitions
Snowflake@1 can also serve lists of definitions: any statement that returns the columns of a test, data source or query definition works. Ready-made table scripts are in Store definitions in a database.
Related
- Technologies — what CAT can test, with the provider behind each.