Hi @mshevelson ,
For our packages (in this case ad_reporting) you can define sources in the dbt_project.yml file instead of sources.yml.
Check out the second half of this post: https://community.fivetran.com/t5/user-group-for-dbt/sources-how-to-prope...
Fivetran's Transformations for dbt Core allows users to trigger model runs after successful connector syncs. Check out our documentation on scheduling options!
In order to take advantage of integrated scheduling, you must have sources properly define...
By default, Fivetran will soft delete records in your warehouse (destination) when we can identify deleted records at the source. This allows analysts the ability to filter for non-deleted records (or deleted) in a staging layer by simply adding w...
If you are looking for potential ways to optimize your transformation time and costs, consider using dbt's incremental models. These models will only transform newly changed rows, which can be identified using Fivetran's system column -> fivetran_syn...
Hi @george_durzi ,
I think I am tracking. Here is what I would do if I was you.
Once your Postgres data lands in Snowflake (ingest db), make sure to use dbt's contracts (https://docs.getdbt.com/reference/resource-configs/contract) and constraints (...
Hi @george_durzi ,
When you say 'destination tables' - which destination are you referring to? I guess I would assume the snowflake reporting db?
Do you mind sharing the logic of your models that aren't giving you expected results?
Thanks
Often times for 'default warehouse test' the solution is to grant usage on that warehouse to that user/role. This is similar to https://fivetran.com/docs/destinations/snowflake/troubleshooting/specify-correct-warehouse-name
If I am understanding your question correctly, it's likely that your google_ads connector is not named google_ads.If you changed the name of your connector to something other than the default, you will need to add a variable in your dbt_project.yml f...
