3655855 - [MSSQLLogReaderAdapter] Handling trigger execution order with custom AFTER triggers - SAP HANA Smart Data Integration

In certain Microsoft SQL Server environments, replicated tables may contain AFTER triggers that modify the same row immediately after an insert or update.

Since the SDI Microsoft SQL Server Log Reader adapter also uses AFTER triggers (_I_SDI_TRIG, _U_SDI_TRIG, _D_SDI_TRIG) to capture changes, the relative execution order of these triggers may influence whether the shadow table reflects the intended final state of the row.

Note: This is only relevant if said AFTER triggers modify the same row as part of their logic (e.g., performs an UPDATE on the newly inserted row). If other non-SDI triggers only perform side actions (e.g., logging), the order does not affect SDI replication. In most systems, AFTER triggers do not modify the same row, so this concern does not apply.

• SAP HANA Smart Data Integration
• Microsoft SQL Server Log Reader adapter (trigger-based mode)

SDI, Smart Data Integration, Microsoft SQL Server, Log Reader adapter, mssqllogreaderadapter, AFTER trigger, trigger order, sp_settriggerorder, inconsistency, shadow table , KBA , HAN-DP-SDI , SAP HANA smart data integration (SDI) , HAN-DP-SDI-DS , SAP Datasphere specific SDI issues , Bug Filed