Skip to main content


Transformations: Trigger tables and New Data Sync for dbt Transformations

Please sign in to leave a comment.



    Common transformations that are integrated with connectors are executed only when new data is processed. This should also be the case for the dbt transformations that are integrated with connectors.

    Running a dbt transformation when there is no new data available is not logical.

    Because the DBT transformation runs at the sync schedule and not on new data arrival there will be costs/credits involved on the database level. Because even though nothing must be transformed (pre and post are same) the transformation runs. These extra costs will be significant when the related SQL is complex and there is a frequent sync and there is only one daily data refresh done.
    Example: Sync of connector is every hour. The exact data delivery is once a day so 23 times there is no new data found. But is runs the DBT transformation 24 times. The execution costs of the SQL on the (cloud) database is therefore charged 24 times. The total database costs/credits increase is significant!

    This is really a showstopper to use Fivetran in the future!

Didn’t find what you need?

Contact support