General Usage Guidelines for Recursive Views - Teradata VantageCloud Lake

Lake - Working with SQL

Deployment
VantageCloud
Edition
Lake
Product
Teradata VantageCloud Lake
Release Number
Published
February 2025
ft:locale
en-US
ft:lastEdition
2025-11-21
dita:mapPath
jbe1714339405530.ditamap
dita:ditavalPath
pny1626732985837.ditaval
dita:id
jbe1714339405530

Updatability of Recursive Views

Recursive views are not updatable.

Controlling the Cardinality Estimate for the Final Recursive Result Spool

The cardinality estimate of the final recursive result spool is controlled by factors established by Teradata Support. If you think your site may benefit from a change to its value, contact your Teradata Support representative.

Stratification of Recursive View Evaluation

Recursive view evaluation is said to be stratified because the system evaluates the seed and recursive statement components (see Components Supported in a View Definition) of a recursive view definition separately.

Specifying RECURSIVE for a Non-Recursive View

The system does not require a view defined explicitly with the keyword RECURSIVE to have a recursive reference. If such a view definition is otherwise correct syntactically, the system creates the view as specified without returning an error to the requestor. However, the resulting database object is not a recursive view.

This is analogous to the situation in which you explicitly define an outer join in your query, but the Optimizer evaluates the query text as if you had defined an inner join, and rewrites it accordingly. In that situation, the system makes an inner join on the specified tables, but does not return an error or a warning to the requestor.

For further details of this Optimizer behavior, see Coding ON Clauses with WHERE Clauses for Outer Joins. To see how to tell if the Optimizer created an outer join plan, see Guidelines for Using Outer Joins.