databricks Platform · Updated Jun 3, 2026

Table update triggers on Delta Sharing and system tables (Beta)

Table update triggers in Lakeflow Jobs can now monitor data shared through Delta Sharing and system tables, in addition to local tables.

Beta Open docs ↗release note ↗

What it does

Table update triggers in Lakeflow Jobs can now monitor data shared through Delta Sharing and system tables, in addition to local tables. You can trigger a job whenever a provider updates a shared table or view, or whenever new operational data lands in a system table. This feature supports Databricks to Databricks Delta Sharing only.

Why it matters

Table update triggers do not incur additional costs other than cloud provider costs associated with listing tables and reading updates from the storage location.

Key capabilities

Table Update Triggers on OpenSharing

Table Update Triggers on OpenSharing (Recipient): A workspace-level beta, enabled in the recipient workspace where the trigger…

Table Update Triggers on OpenSharing

Table Update Triggers on OpenSharing (Provider): An account-level beta, enabled in the provider account that owns the shared data.

Limitations · remember

!Views that use readfiles (they can read from a supported table that reads files, but cannot directly use readfiles).

!Views that depend on tables that are not in Unity Catalog.

!Views that depend on federated tables. Creation of triggers for views containing unsupported dependencies still succeed, but no job runs are triggered when an unsupported dependency is updated. Table update triggers monitor changes to the dependent tables of a view and considers the view updated if any of the dependent tables is updated. It is possible for a job run to be triggered for data changes that are filtered out by the view definition. Source tables for a view are counted towards the limit of 10 tables per trigger.

!For example, if a view depends on 11 tables, it is not possible to use it in a table update trigger. Similarly a trigger with two views, each of which depends on 6 tables, counts as 12 tables. There is a separate limit of 10 dependent views per monitored view.

!For example, if a view depends on 11 other views, it is not possible to use it in a table update trigger, even if this does not break the 10 tables per trigger rule.

Architecture

Databricks Platform → Platform

In short

Read the full documentation ↗

Key takeaway

Table update triggers in Lakeflow Jobs can now monitor data shared through Delta Sharing and system tables, in addition to local tables.

2026-06-03-table-update-triggers-on-delta-sharing-and-system-tables-beta Generated by the Databricks Updates Agent · browse all updates