Snowflake support

Last updated date:

Connect, reconnect, and troubleshoot Snowflake without sharing credentials or customer content through support channels.

1. Before you start

  • Create a dedicated service user and role, assign the RSA public key, and retain the matching private key securely.
  • Grant warehouse/database/schema USAGE and REFERENCES only for approved metadata populations.
  • Add optional Snowflake governance viewer roles only when account-level authorization diagnostics are approved; configure database/schema filters explicitly.
  • Do not send Snowflake credentials, customer content, personal information, or private record data by email or through an ordinary support ticket.
Snowflake key-pair authenticationSnowflake's key-pair authentication guidance.

2. Connect Snowflake

  1. In Seedling, open Connections and choose Snowflake.
  2. Connect from workspace scope as a current Seedling workspace administrator.
  3. Enter the account identifier, service username, PEM private key and optional passphrase, role, warehouse, default database/schema, include/exclude filters, and SQL API URL.
  4. Seedling signs SQL API requests, verifies the account and role context, and runs only checked-in metadata queries.
  5. Allow the first Snowflake synchronization to finish, then verify the expected resource population and member access policy.

3. Authorization and connection problems

Snowflake key pair rejected
Confirm the snowflake key pair is active, was entered without surrounding whitespace, and belongs to the intended Snowflake account and environment.
Missing permission or resource
Restore the exact read permission or provider-side resource access described in this guide. Seedling does not substitute a broader credential or silently treat a forbidden Snowflake population as empty.
Wrong account or scope
Disconnect before retrying with the intended Snowflake identity, account, and Seedling connection scope. Seedling does not infer account ownership from a display name or email address.

4. Missing or delayed data

  1. Confirm the selected role retains warehouse, database, and schema USAGE plus REFERENCES for the affected relation.
  2. Check include/exclude filters, managed-access schema behavior, role inheritance, and account/database role activation.
  3. Do not add table SELECT to solve missing metadata; correct the metadata grants and filters.
  4. Allow incremental synchronization and provider retry handling to complete. A temporary provider failure does not delete previously synchronized data.
  5. If the issue remains, contact support@tryseedling.ai with the Seedling workspace, safe timestamps, and non-sensitive provider record identifiers. Do not include credentials or record contents.

5. Rotate or replace access

Never use email or an ordinary support ticket to transfer the old or replacement credential.

  1. Create replacement snowflake key pair for the same Snowflake account with the same or narrower released permissions.
  2. Replace the credential on the exact Seedling connection and repeat identity, scope, and capability verification.
  3. After Seedling confirms the replacement, revoke the old snowflake key pair in Snowflake.