Connector Improvement: SQL Server Destination Schema Prefix with Source Naming
Answered
The UI of the connector configuration for SQL Server is misleading. It is not clear that the Destination Schema Prefix only applies when the Five Naming option is used for the Destination Schema Names. We would like to leverage a prefix with all other aspects of the source schema and object names being retained.
Use case: We land all of our data in a single staging database in Snowflake for production (Fivetran_PROD) and a single staging database for non-production (Fivetran_DEV). We want to leverage the prefix to organize the destination by source system (ex. systemType_systemName_environment) and have it append the schema (ex. mssql_systemName_DEV_dbo or mssql_systemName_QA_dbo), while not accepting the other naming changes that Fivetran will implement if Fivetran naming is selected. For example, fivetran naming will lower-case all object names.
-
Official comment
Hi Brandon,
The source name approach was designed to support use cases where customers want the destination to mirror the structure of the source. Your scenario falls somewhere between the two existing options—source naming and Fivetran naming. Unfortunately, this scenario can’t be implemented with the current configuration. As an alternative, you might consider renaming the schema directly in your Snowflake destination.
We've added clarification to the connector documentation about how the prefix is applied—thanks for pointing that out!
Please sign in to leave a comment.
Comments
1 comment