The problem I’m having I have 2 models that are inserting into the same table of my warehouse. (schema='my_schema', alias='my_table', materialized='incremental', incremental_strategy='append') It raises me the error: dbt found two resources with the database representation "my_schema.my_table". …

Can you create an intermediate model that joins your two resources, then use that model as the ref for your incremental?

the two resources don’t necessarily run at the same time.

But if your models are idempotent, it shouldn’t matter if you run them twice; so you can run them once when resource1 is updated, and a second time when resource2 is updated.

why does dbt raise me an error if it’s not an issue?

What is not an issue, or shouldn’t be an issue, is running a model more than once… even if the data hasn’t changed. This is following the logic I mentioned above about having an intermediate model joining your 2 sources. What is an issue, and you won’t be able to do, is to have two models with the …

And that’s the point of my question. To insert into a table in different ways, I’m using “insert models”. For every insert models, I’m using the same alias. Each insert model select info from some models (these selected models differ depending of the insert model). The names of the insert models a…

I have the same problem when migrating a job from an old ETL tool to dbt. In the old ETL tool, there are many cases that required separate jobs to insert/update into the same 1 table. In dbt, that won’t be allowed, only 1 model per table. Based on my experience, there are some ways to work around. …

This feels to me like you would want to build a customised materialization

My first thought is that you could have each model write into separate tables, then schedule another model that unions these two tables. This is similar to quangbilly79’s staging layer solution.

dbt requires that each resource in your project has a unique database representation (the combination of database.schema.identifier). If two resources resolve to the same database.schema.alias, dbt will raise the error: dbt found two resources with the database representation my_schema.my_table. db…

Migrating a ETL to DBT: Target table conflict

Help

aditya June 8, 2026, 4:25am 17

so you have to pass different combination of db.schema.identifier

Topic		Replies	Views
How to design 2 seperated dbt job write to the same table? DBT won't allow duplicate model file name Help dbt-core	4	233	September 16, 2025
Error when same variable is used in target of 2 different models Help	3	2001	February 21, 2023
Compilation Error dbt found two models with the name Archive	2	13435	July 8, 2022
Is it possible to have multiple files with the same name in dbt? Help alias	1	16870	October 17, 2019
Is there a way to have two different models coexist that is writing to same table? Help jinja , snowflake , dbt-cloud	4	10767	March 15, 2023

Migrating a ETL to DBT: Target table conflict

Related topics