Understand dbt model materializations.
Materializations define how a particular model is persisted in the data warehouse. Y42 offers two primary options for materialization: views and tables. It is not recommended to use the third option, ephemeral, due to how Y42 abstracts the data warehouse layer.
Views are the most cost-effective materialization type as they only persist the query and not the data itself. For example. when a scheduled build configured with only materialized views runs, it executes
CREATE VIEW statements against the data warehouse without processing any data.
Materializing models as tables can speed up data access, especially when model execution is slowing down. For example, creating tables at the end of a data pipeline enables faster queries as data consumers only need to run the last model, instead of all upstream models.
Incremental models are built as tables, but unlike full-table materializations, incremental models update only new or changed rows in a data table, making data processing significantly faster and more efficient.
For more in-depth information about incremental models, please follow this link.
Ephemeral materialization injects models as Common Table Expressions (CTEs) inside downstream tables.
By default, dbt models are materialized as views. However, you can customize this setting by introducing the
materialized YAML configuration parameter:
You can also configure a model's materialization type using a configuration block in its