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

Community

Connector Improvement: SQL Server Connector to pick destination Schema

Wai Chin User

The current setup of SQL Server connector mandated to pick a non-editable prefix.  While the major reason for this prefix is to ensure the uniqueness of the schema name, but it is not allowing to pick the destination schema like the other connectors.

 

This is not handy for the use case to migrate from on-premise database to a cloud base Datawarehouse such as Snowflake.  Many of our dashboards in Looker already built and using the table/schema name without the prefix.  A lot of manual change is needed.

 

It will be a huge improvement, if allowing the SQL Server connector to have the same feature as the other connectors, to pick the destination schema instead of forcing adding a prefix.

Please sign in to leave a comment.

Comments

1 comment

Date Votes
  • Official comment
    Kevin Kim Fivetranner

    Hi Wai,

    Thank you for your feedback on our feature request portal! As you mentioned, the prefix is used today to ensure uniqueness, however, I agree it is odd that database connector naming conventions differ from our other connector types. I will be sure to discuss this with our team internally but don't have a set timeline for when we would prioritize this request.

    Also, we are reviewing our naming conventions and renaming rules so I will raise this as part of that investigation as well. Please stay tuned as we evaluate feature requests and projects regularly!