Create View Component

Create View Component



Create View Component

The Create View component allows you to output a view definition to the Redshift cluster. In some circumstances, this action may be preferable to writing the data to a physical table.

The Create View component allows you to output a view definition to the Snowflake warehouse. In some circumstances, this action may be preferable to writing the data to a physical table.

The Create View component allows you to output a view definition to the Big Query Project. In some circumstances, this action may be preferable to writing the data to a physical table.

If there is an existing view with the same name, it will be replaced. If there is an existing table with the same name, then the step will fail - it will not replace an existing table, only a view.

The views created by this component are somewhat isolated from the other views created as part of a normal operation. It will NOT be dropped when the job is re-validated, but will be recreated at runtime when the job is executed.

Note:This component cannot create views using external schemas.


Redshift Properties

Property Setting Description
Name Text The descriptive name for the component.
Schema Select Select the table schema. The special value, [Environment Default], will use the schema defined in the environment. For more information on using multiple schemas, see this article.
View Name Text Any valid view name.
Late binding Select If set to Yes, creates a late-binding view. Late-binding views do not check referenced tables until queried. As such, late-binding views can reference external tables and are not automatically dropped when the underlying table is dropped.

Snowflake Properties

Property Setting Description
Name Text The descriptive name for the component.
Database Select The name of the database that the new view belongs to.
Schema Select Select the table schema. The special value, [Environment Default], will use the schema defined in the environment. For more information on using multiple schemas, see this article.
View Name Text Any valid view name.
Secure View Select 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 Select 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.

BigQuery Properties

Property Setting Description
Name Text The descriptive name for the component.
Project Text The name of the Google Cloud Project the source table exists on.
Dataset Select Select the table dataset. The special value, [Environment Default], will use the dataset defined in the environment.
For more information on Google Cloud Datasets, visit the official documentation.
View Name Text Any valid view name.

Synapse Properties

Property Setting Description
Name Text The descriptive name for the component.
Schema Select Select the table schema. The special value, [Environment Default], will use the schema defined in the environment.
For more information on schemas, please see the Azure Synapse documentation.
View Name Text Any valid view name.

Strategy

Generates a permanent, named view, containing the SQL generated by all the input tables up to the Create View component.

Example

This example creates a view over the Accounts table, applying a filter to select New Accounts.

Only the View Name needs to be completed:

Whenever "new_accounts_view" is read, it will reflect the current contents of the Accounts table with the filter applied.