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

Community

Connector Improvement: Separate Metadata from Sync data for Snowflake connector

Neil McCallum User

Hi,

We're an HVR customer, but evaluating Fivetran for salesforce -> snowflake.

We prefer the way the HVR deals with sync metadata in two ways.

1. In HVR the sync tables in the destination can be managed in their own schema which keeps the schemas which are being synced cleaner and more reflective of the actual sources.

2. In HVR the rows are delivered without attached sync metadata, which simplifies our datalake -> datavault operations as we don't have to discount sync metadata explicitly.

I appreciate these might be quite core design decisions and there are also potential reliability benefits in transacting the sync metadata and data together but the difference was unexpected and in my view inferior to the sister product.

Please sign in to leave a comment.

Comments

1 comment

Date Votes
  • Official comment
    Meera Fivetranner

    Hi Neil,

    Thank you so much for reaching out to Fivetran. We currently have a Fivetran Platform Connector that has the sync information including the number of records processed and modified. In addition, the connector provides insight into the metadata of what's being synced as well. Fivetran Platform Documentation

    As I understand, there's specific metadata that's required of the Salesforce -> Snowflake connection. We'd love to understand in a bit more detail the use case. How is the sync metadata being used and is there specific metadata that would be most valuable to the team?

    Thank you,

    Meera