Materialization Decision Guide: Comparison Matrix¶
This table presents the available options to materialize data. This will help you choose the most appropriate materialization option for your use case.
Summary |
Full Materialization |
Query Results (pka partial) |
|
|---|---|---|---|
Use cases |
|
|
|
Usage |
Dynamic: Optimizer can decide to leverage a Summary on a query execution |
Always. Data is always retrieved from materialization. |
From materialization if possible. Otherwise from underlying source. |
Linked to the logical model |
Full lineage, invalidation on changes |
Full lineage, invalidation on changes |
Full lineage, invalidation on changes |
Data Load mechanisms |
|
|
|
IDU |
N/A |
N/A |
N/A |
Target Materialization |
Any |
Cache data source |
Cache data source |
Table life duration |
Manual drop |
|
|
Remote Tables |
Temporary Tables |
Materialized Tables |
|
|---|---|---|---|
Use cases |
|
|
|
Usage |
Always from remote table |
Always from temporary table. Only available to the user session |
Always from materialized table. For specific scenarios. |
Linked to the logical model |
Only the SQL query used |
None |
None |
Data Load mechanisms |
|
Explicit |
Explicit |
IDU |
Insert, Delete, Update |
Insert |
Insert |
Target Materialization |
Any |
Cache data source |
Cache data source |
Table life duration |
Permanent (Can be manually dropped) |
Session |
Permanent (Can be manually dropped) |
