All Collections
Connect your databases
Troubleshoot Snowflake database connections
Troubleshoot Snowflake database connections

Steps to solve issues connecting your Snowflake database to Geckoboard.

Updated over a week ago

If you cannot connect to your Snowflake database in Geckoboard using our Databases data source, this may be due to an incorrect account URL format.

Requirements for connecting Snowflake

To connect successfully to Snowflake, you must have a predefined default role with USAGE rights on the required databases and an associated default warehouse. This approach avoids potential complications from using nested roles or custom role selections.

In summary, you need to:

  1. Select a pre-assigned default role. This role determines the user’s permissions in Snowflake. Snowflake offers an option to use a custom role during connection, but Geckoboard doesn’t support this feature.

    The user should have a pre-assigned default role in Snowflake
  2. Assign USAGE privileges for the default role on the intended databases. USAGE privileges allow a user or role to access the specified database. Without it, the connection will fail.

    Assign USAGE privileges for the default role on the intended databases.
  3. Avoid using nested roles in Snowflake. Snowflake supports hierarchical or nested roles. For instance, a higher-level role might have sub-roles with specific permissions. Geckoboard doesn’t use these nested roles. Instead, during the connection process, we utilize the default role assigned to the user.

  4. Assign a default warehouse. If not, the warehouse should be specified at the time of connection in the Geckoboard connection panel.

Find your account URL in Snowflake

You can find your account URL in Snowflake by clicking your account name in the bottom left of the screen and then copying the account URL.

Then, paste your account URL, without any modifications, into the Account URL field in the database connection panel in Geckoboard.

Error: The requested database does not exist or is unauthorized

If you're receiving the error "The requested database does not exist or is unauthorized", this either means that it doesn't exist or the user is not part of a role that has USAGE privileges on the specified database.

Did this answer your question?