A query asset is a dynamic view of a data asset that is created based on an SQL query. Such data asset can contain data from one or more tables in a single data source, or a subset of rows from a single table.

With dynamic views, you have these options:

• You can create a data asset that contains a subset or a superset of columns based on column selection, an explicit set of rows based on a conditional expression, or a combination of both.
• You can split a table into several smaller data assets based on the values in a selected column.

Extracting only relevant data improves security and usability of your data. Users have quick access to the specific data they need.

You can use the resulting assets in the same way as a regular connected data asset:

• As a data scientist, you can use such assets in Data Refinery.

• As a data steward, you can profile and enrich such assets through metadata enrichment.

• As a data quality analyst, you can run data quality analysis on such assets.

After you create a dynamic view, you can see this information when you click the asset name:

• The asset name and description.
• The table type.
• The tags for the asset.
• The containing folder.
• The connector type.
• The SQL query that generates the asset. You can edit the SQL query by clicking the pencil icon. After you edit the SQL query, you might need to rerun profiling or metadata enrichment, and update and rerun any data quality rules for the asset.
• When the asset was last modified and by whom.
• When the asset was added to the project and by whom.
• A preview of the selected data.
• A profile of the selected data.
• Data quality information for the selected data.
• Visualizations.
• Feature groups.

Currently, you can't publish a dynamic view to a catalog, promote it to a deployment space, or create a masking flow for it.