Skip to main content

Community

Add ability to change the name of a connector and the destination schema

Answered

Please sign in to leave a comment.

Comments

2 comments

  • Official comment

    Hi John,

    Thanks for your post here! I'll likely split these into two separate requests since they would be implemented differently: changing connection names and changing schema names

    Between the two, which is the higher priority? would love more context on your scenario!

    Hi Kevin -  context is that we're migrating to snowflake over the course of a couple years.  We've got many different data sources, both internal and external.  Our naming standards are a bit constrained by source db & schema names, and Fivetran naming flexibility.  (example, tables from sql server with different DBO must go into separate snowflake destination schemas).  That's understandable.  But during gradual migration of many sources, it's been hard to plan good naming standards.  We've run across connector and destination schema names we'd like to change without deleting and starting over.   I hope that makes sense.

    As for priority, I'd say they're equal for us, but I imagine the connector name might be easier to implement.