Dynamic tables: New behavior for cloned dynamic tables (Preview)¶

Attention

This behavior change is in the 2025_03 bundle.

For the current status of the bundle, refer to Bundle History.

Cloned dynamic tables behave as follows:

Before the change:

Cloned dynamic tables assume the same state (ACTIVE or SUSPENDED) as the source dynamic tables.

After the change:

Cloned dynamic tables are suspended by default, whether you clone a dynamic table directly or clone a database or schema that contains dynamic tables.

In the output of the DYNAMIC_TABLE_GRAPH_HISTORY table function, their SCHEDULING_STATE column shows CLONED_AUTO_SUSPENDED as the reason_code. Any dynamic tables created downstream to these cloned dynamic tables are also suspended, with a reason_code of UPSTREAM_CLONED_AUTO_SUSPENDED.

For more information, see Automatic dynamic table suspension.

Ref: 1943