REFRESH ANALYTICAL VIEW; Partition-Based

After creating an analytical view, you must populate it with data using the REFRESH operation. You must also refresh the analytical views as the base table data changes.

This article describes how to refresh partition-based analytical views. For sequence-based analytical views, see REFRESH ANALYTICAL VIEW; Sequence-Based.

This topic contains the following sections:

Syntax

REFRESH [ALL] ANALYTICAL VIEW[S] [LIKE pattern| analytical_view_name];

Parameter

analytical_view_name
The name of the target analytical view
pattern
This is a quoted string literal, using * (wildcards) and | (pipes) for alternation. The LIKE keyword is optional. The system stores object names in lowercase.

Notes

ALL

The keyword ALL affects all analytical views in the cluster.

We recommend that you avoid this operation unless completely necessary, as it may be very computationally intensive and time consuming.

Examples

Refreshing All Analytical Views in the Cluster
REFRESH ALL ANALYTICAL VIEWS
Refresh All Analytical Views in the Current Database
REFRESH ANALYTICAL VIEWS
Refresh All Analytical Views in the Current Database with Names that Start with the Specified String
REFRESH ANALYTICAL VIEW LIKE 'av_sales*'
Refresh the Specified Analytical View

The following command refreshes a specific analytical view in the current database:

REFRESH ANALYTICAL VIEW av_sales;

Alternatively, this command refreshes an analytical view in a specific database, while connected to any database:

REFRESH ANALYTICAL VIEW sales_data.av_sales;