Dynamic tables: New column in SHOW DYNAMIC TABLES and DDL fix (Pending)¶

Attention

This behavior change is in the 2026_02 bundle.

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

When this behavior change bundle is enabled, the SHOW DYNAMIC TABLES command includes a new BACKFILL_FROM column, and the generated Data Definition Language (DDL) for dynamic tables preserves the user-provided table from the BACKFILL_FROM attribute.

SHOW DYNAMIC TABLES command: New column in output¶

When this behavior change bundle is enabled, the output of the SHOW DYNAMIC TABLES command includes the following new column:


Column name	Data type	Description
BACKFILL_FROM	VARCHAR	The backfill source table, if specified. For example, `table`, `schema.table`, or `db.schema.table`.

Before the change:: BACKFILL_FROM is only visible inside the DDL string in the description column. Detecting backfill configuration changes requires parsing raw SQL.
After the change:: BACKFILL_FROM is a standalone column, giving you direct programmatic access to the backfill configuration.

DDL consistency fix¶

When this behavior change bundle is enabled, the generated DDL for dynamic tables behaves in the following manner:

Before the change:: If you create a dynamic table with a fully or partially qualified table name—for example, CREATE DYNAMIC TABLE ... BACKFILL FROM my_schema.my_table—the generated DDL might strip the schema and display only my_table. This inconsistency can cause issues during redeployments.
After the change:: If you create a dynamic table with a fully or partially qualified table name—for example, CREATE DYNAMIC TABLE ... BACKFILL FROM my_schema.my_table—the generated DDL preserves the exact qualification you provided. If you specified my_schema.my_table, the DDL reflects my_schema.my_table.

Ref: 2248