Health Tab: Trigger Detection button vs. Sync Data Policies

A handler is a wrapper around the metadata describing an ODBC connection. i.e. there is a handler for each Snowflake schema project where the connection string must be unique for each handler, e.g: [email protected]:443/databasename

Question

When selecting a DataSource under the “Healthy” dropdown what is the difference between the “Trigger Detection” and “Sync Data Policies” buttons?

Answer

Sync Data Policies calls /handler/{handlerId}/refreshNativeViewJob which calls bulkRefreshNativeViews()

• Scope: works against a handler. So everything associated with the handler is impacted

• Updates only Data policies (however will update both Data and Subscription policies IF table grants is disabled)

• Does not check privileges of user running. Assumes user has privileges to author and update data policy

Trigger Detection calls /dataSource/detectRemoteChanges endpoint

• Scope for this specific button is just the single dataSource for which you are examing the Health for

• Updates both Subscription and Data policy