Snowflake

Data Source Details

Use the following information when creating a data source for your Snowflake database:

• The JDBC URL must be in the following format:

  jdbc:snowflake://<db_account>.snowflakecomputing.com:<db_port>?warehouse=<db_warehouse>&db=<db_name>

• Basic authentication is supported. Specify user and password.

• If you use native authentication inside your cloud platform (for example, Google Cloud Platform, Amazon Web Services, or Microsoft Azure), you do not have to provide the username and password.

GoodData uses the driver with version 3.13.21.

User Access Rights

We recommend that you create a dedicated user and user role for integration with the GoodData platform.

Steps:

1. Create a user role and grant the following access rights to it.:

   GRANT USAGE ON WAREHOUSE {warehouse_name} TO ROLE {role_name};
   GRANT USAGE ON DATABASE {database_name} TO ROLE {role_name};
   GRANT USAGE ON SCHEMA {database_name}.{schema_name} TO ROLE {role_name};
   GRANT SELECT ON ALL TABLES IN SCHEMA {database_name}.{schema_name} TO ROLE {role_name};
   GRANT SELECT ON FUTURE TABLES IN SCHEMA {database_name}.{schema_name} TO ROLE {role_name};
   GRANT SELECT ON ALL VIEWS IN SCHEMA {database_name}.{schema_name} TO ROLE {role_name};
   GRANT SELECT ON FUTURE VIEWS IN SCHEMA {database_name}.{schema_name} TO ROLE {role_name};
   

   If you intend to enable pre-aggregation caching, additional usage rights have to be granted for your pre-aggregation schema cache_schema_name:

   GRANT USAGE, CREATE TABLE ON SCHEMA {database_name}.{cache_schema_name} TO ROLE {role_name};
   

2. Create a user and grant it with the user role:

   GRANT ROLE {role_name} TO USER {user_name};
   

3. Make the user role default for the user:

   ALTER USER {user_name} SET DEFAULT_ROLE={role_name};
   

Performance Tips

If your database holds a large amount of data, consider the following practices:

• Denormalize the relational data model of your database.

  This helps avoid large JOIN operations. Because Snowflake is a columnar database, queries read only the required columns and each column is compressed separately.

• Spin up databases/instances based on user needs.

  • Users with similar needs populate data into caches that are likely reused.
  • Isolate data transformation operations running in your database from the analytics generated by GoodData.

• Set up proper auto-scaling based on users needs.

• Utilize materialized views

  • Changes to underlying tables are propagated to related materialized views, they are always consistent
  • Materialize results of JOINs / aggregations which are executed very often as a result of execution of dashboards / visualizations from GoodData
    • Map materialized views and their columns to datasets and LDM and utilize them in metrics / visualizations / dashboards

Query Timeout

Query timeout is configurable per application instance. It is a parameter of the sql-executor service, default value is 160 seconds.

Query timeout is closely related to the ACK timeout. Proper configuration of the system requires that ACK timeout is longer than query timeout. Default ACK timeout value is 170 seconds.

Permitted parameters

• application
• db
• loginTimeout
• networkTimeout
• ocspFailOpen
• passcode
• passcodeInPassword
• useProxy
• proxyHost
• proxyPort
• proxyUser
• proxyPassword
• proxyProtocol
• queryTimeout
• role
• stringsQuotedForColumnDef
• token
• warehouse