Create View
The Create View component enables you to output a view definition to your cloud data warehouse (CDW). In some circumstances, this action may be preferable to writing the data to a physical table.
If a view of the same name already exists, it will be replaced when this component runs.
If a table of the same name already exists, this component will fail its run—the Create View component cannot replace an existing table, only an existing view.
Views created by this component will not be dropped when the Transformation Job is revalidated. However, the views will be recreated at runtime (when the Transformation Job is executed).
Note
This component cannot create views using external schemas.
Properties
Name = string
A human-readable name for the component.
Database = drop-down
The Snowflake database. The special value, [Environment Default], will use the database defined in the environment. Read Databases, Tables and Views - Overview to learn more.
Schema = drop-down
The Snowflake schema. The special value, [Environment Default], will use the schema defined in the environment. Read Database, Schema, and Share DDL to learn more.
View Name = string
Provide a name for the view to be created.
Secure View = drop-down
When Yes, the view definition and details are only visible to authorised users, i.e. users who are granted the role that owns the view. Default is No.
Snowflake advises that views should be defined as secure when they are specifically designated for data privacy. For more information about secure views, please read the Snowflake documentation.
View Type = drop-down
- Materialized: A materialized view is a pre-computed data set derived from a query specification and stored for later use. Since the data is pre-computed, querying a materialized view is faster than executing the original query. Materialized views are advised when:
- Query results contain a small number of rows and/or columns relative to the base table.
- Query results contain results that require significant processing.
- Standard: (default setting) create standard views when:
- The results of the view change often.
- The results are not used often (relative to the rate at which the results change).
- The query is not resource intensive, so it is not costly to re-run it.
Name = string
A human-readable name for the component.
Catalog = drop-down
Select a Databricks Unity Catalog. The special value, [Environment Default], will use the catalog specified in the Matillion ETL environment setup. Selecting a catalog will determine which databases are available in the next parameter.
Database = drop-down
Select the Delta Lake database. The special value, [Environment Default], will use the database specified in the Matillion ETL environment setup.
View Name = string
Provide a name for the view to be created.
Table Properties = column editor
- Key: A metadata property within the table. These are expressed as key=value pairs.
- Value: The value of the corresponding row's key.
Comment = string
A descriptive comment of the view.
Name = string
A human-readable name for the component.
Schema = drop-down
Select the table schema. The special value, [Environment Default], will use the schema defined in the environment. For more information on using multiple schemas, read Schemas.
Late Binding = drop-down
Selecting "Yes", creates a late-binding view. Late-binding views do not check underlying database objects, such as tables and other views, until the view is queried. As a result, users can alter or drop the underlying objects without dropping and recreating the view. If the user drops underlying objects, queries to the late-binding view will fail. If the query to the late-binding view references columns in the underlying object that aren't present, the query will fail.
The default setting is "No".
View Type = drop-down
- Materialized: A materialized view is a pre-computed data set derived from a query specification and stored for later use. Since the data is pre-computed, querying a materialized view is faster than executing the original query. Materialized views are advised when:
- Query results contain a small number of rows and/or columns relative to the base table.
- Query results contain results that require significant processing.
More information can be found here.
- Standard: (default setting) create standard views when:
- The results of the view change often.
- The results are not used often (relative to the rate at which the results change).
- The query is not resource intensive, so it is not costly to re-run it.
More information can be found here.
Name = string
A human-readable name for the component.
Project = drop-down
Select the Google Cloud project. The special value, [Environment Default], will use the project defined in the environment. For more information, read Creating and managing projects.
Dataset = drop-down
Select the Google BigQuery dataset to load data into. The special value, [Environment Default], will use the dataset defined in the environment. For more information, read Introduction to datasets.
View Name = string
Provide a name for the view to be created.
View Type = drop-down
Select the view type:
- Materialized: materialized views in Google BigQuery are pre-computed views that periodically cache the results of a query for increased performance and efficiency. Queries that use materialized views are typically faster and consume fewer resources compared to queries that retrieve the same data only from the base table. Materialized views can greatly improve the performance of workloads that bear the characteristics of common and repeated queries. For more information, read Introduction to materialized views.
- Standard: a view is a virtual table defined by an SQL query. You create a view by querying it in the same manner you query a table. When you query a view, the query results only contain data from the tables and fields specified in the query that defines the view. For more information, read Introduction to views.
Enable Refresh = drop-down
Select whether to enable refreshing of the materialized view.
- No: The materialized view will only be refreshed manually. For example, when the Create View Transformation Job is re-run, or when triggered by the Refresh Materialized View component.
- Yes: The materialized view will be refreshed automatically every 30 minutes. Example changes would be row insertions or row deletions.
The default setting is Yes.
Name = string
A human-readable name for the component.
Schema = drop-down
Select the table schema. The special value, [Environment Default], will use the schema defined in the environment. For more information on schemas, read the Azure Synapse documentation.
View Name = string
Provide a name for the view to be created.
Strategy
Generates a permanent, named view, containing the SQL generated by all the input tables up to the Create View component.
| Snowflake | Delta Lake on Databricks | Amazon Redshift | Google BigQuery | Azure Synapse Analytics |
|---|---|---|---|---|
| ✅ | ✅ | ✅ | ✅ | ✅ |