This is an on-behalf request for Hitachi Energy.

The customer is aware of the /N/FIVETRAN/TRIGGERS transaction, which allows a trigger to be re-created while suppressing a re-sync. However, for them the main challenge is not the remediation itself, but the visibility of the event.

On Production, this process will be handled through internally agreed operational procedures.

For non-production environments however, they would prefer to rely on SAP mechanisms to automatically drop triggers whenever required by a DDL change. The difficulty is that, without visibility into which objects had their triggers automatically dropped, they would not know where trigger re-creation is required to prevent an unnecessary re-sync.

Their request is for Fivetran to capture and alert for such events, more specifically: 

• Send an alert, when Fivetran detects that a trigger has been automatically dropped by SAP due to a DDL change.
• Make monitoring customizable to selected high-volume / large tables (allow some customization options).
• An alert should be generated soon after the trigger is dropped. (Note: I believe we can only tell during our first run after this event).

Thank you!