This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreDid you hear? There's a new SQL AI Developer certification (DP-800). Start preparing now and be one of the first to get certified. Register now
I have a DBT project that is creating an Incremental table in a Microsoft Fabric warehouse. In the config section of my model, I am specifying the schema to 'gold'. However, "--remove concatenation logic
gold" is the schema created in the warehouse. Could you let me know why this is happening and why my table isn't being created in the 'gold' schema?
The Python packages installed are:
Core:
- installed: 1.11.7
- latest: 1.11.7 - Up to date!
Plugins:
- fabric: 1.9.8 - Up to date!
Solved! Go to Solution.
Thank you,
The issue stemmed indeed from the generate schema macro. Thank you again for identifying this for me.
Thank you,
The issue stemmed indeed from the generate schema macro. Thank you again for identifying this for me.
Hi @salano ,
Thank you for your valuable insights and guidance. I appreciate your support in helping me move forward in the right direction.
Thank you.
Hi @salano ,
Hi, thank you for providing the details of your issue. Based on your description, the behavior you're experiencing appears to be related to how dbt manages schema naming, rather than an issue with the warehouse itself. In dbt, the schema value set in the model configuration is processed by the generate_schema_name macro, which may modify or combine the schema name according to your target settings or adapter logic.
It seems that additional text, such as remove concatenation logic, is being included as part of the schema name. This typically occurs if there is unintended text or formatting in your model file, or if the adapter interprets something unexpectedly. As a result, dbt creates a schema using the entire string instead of just gold.
To address this, please review your model files and configurations for any stray text or comments that may be inadvertently included. Additionally, check if the Fabric adapter applies any extra schema naming conventions. If you want the schema to always be exactly gold, consider overriding the generate_schema_name macro in your project to ensure it returns only the desired schema name without concatenation.
This approach aligns with dbt’s schema management design, and making these adjustments should help you achieve the expected outcome.
Thank you.
Check out the April 2026 Fabric update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
| User | Count |
|---|---|
| 15 | |
| 11 | |
| 6 | |
| 6 | |
| 5 |