FAQ

What tables are accessed by Sifflet, and how are they used?

Sifflet accesses various tables in your Snowflake account to provide a complete user experience. Restricting access to some of those databases/schemas/tables might reduce the number of functionalities Sifflet provides.

I refreshed the Snowflake sources on Sifflet but some of my latest SQL transformations, tags, etc. do not appear. Why?

Snowflake declares a range data latency times due to the process of extracting the data from Snowflake’s internal metadata store.

Overall, for ACCOUNT_USAGE tables, you should expect a latency of up to 3 hours from Snowflake. For more detailed information, please refer to the "Data latency" section of the Snowflake Account Usage documentation..

My Snowflake source on Sifflet indicates that some permissions are missing, why ?

When using the Test Connection feature or when refreshing a source, Sifflet will check that required permissions are correctly configured. The required permissions are described in the Integration guide of this page.

To troubleshoot missing permissions, you can use the command SHOW GRANTS TO ROLE $role_name (or SHOW FUTURE GRANTS TO ROLE $role_name for future permissions), to see if the correct privileges were granted on the correct objects.

Note that if you are connected to Snowflake with your personal user, are using the Sifflet role and can query objects that the Sifflet role should not have access to, this is because of the Snowflake Secondary roles feature which adds to the context all of the roles granted to the user to determine the available permissions. If you want to run queries using only the Sifflet role, use the following query to disable the Secondary roles feature: USE SECONDARY ROLES NONE. After troubleshooting, you can run USE SECONDARY ROLES ALL to re-enable the feature.