Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Connector Improvement: Create schema required for snowflake destination

Answered
Arvind Misra User
The Snowflake connector currently requires a role with CREATE SCHEMA privileges. However, if the destination schema already exists, this permission should not be necessary. Despite the schema being pre‑created, the destination setup still fails, and the connector is unable to complete the destination creation successfully.
Destination creation should not validate for create schema access if schema already exists.

Please sign in to leave a comment.

Comments

2 comments

Date Votes
  • Egidio Terra Fivetranner

    Hi Arvind,



    Thanks for raising this connector improvement request. To help us better understand the underlying needs, could you elaborate on the problem you are trying to solve by removing the CREATE SCHEMA privilege requirement when the schema already exists? Additionally, are there specific external regulations or policies that require this adjustment to privilege management in your environment?



    Understanding your exact requirements and any compliance factors will help us assess potential changes to the connector setup flow.



    Thanks,

    Egidio

  • Arvind Misra User

    Hi Egido

    We have the following concerns regarding granting CREATE SCHEMA privileges to the Fivetran role:

    CREATE SCHEMA grants the Fivetran role access to grant privs for objects in the schema outside of the established process due to the ownership privs at the schema level

    CREATE SCHEMA comes with other implicit privs that we do not want to grant because of org standards (like create tasks, create external stages, create mat views etc)

    we have communicated same to our fivetran proserv partners