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

Community

Other: Please make the column ordinal positioning in Destination (after FIVETRAN sync) match with the Source Database column ordinal positioning.

Answered
Prazna Agnihotram User
  • Edited

Please make the column ordinal positioning in Destination (after FIVETRAN sync) match with the Source Database column ordinal positioning. Right now, after the fivetran sync is done...the column ordinal positioning is changing randomly in destination and it makes it difficult when we do data comparison exercises between Source data & Destination data.

Please sign in to leave a comment.

Comments

3 comments

Date Votes
  • Official comment
    Kevin Kim Fivetranner

    Hi Prazna,

    Thank you for your question! Would you have more details on your use case for this request?

    As you mentioned, we do not have an explicit order when we are loading data into the data warehouse. Could you help explain the main pain point you are facing in this situation?

  • Helen Casier User

    We bring in data from to different Pharmacies that have independent databases, but same schema. Then on our side we create a unions to get a unified view of the tables. When the order is different between the the tables ,the union is not working. We would prefer if there was a way to persist the original column order rather than having to explictly list all the ocolumns.

  • Andrew Taft User

    This feels like a bug rather than a feature request. In the EL part of ELT, the source and destination table should have the same column ordinal positioning. At the very least, the different ordering is making it difficult for people who are familiar with the source schemas. Ordinal positioning is one of the core tenets of databases.