JDBC Delta Aggregation without a separate delta table - using last modified date column instead

I’d like to implement Delta Aggregation using a “last modified date” column instead of creating a separate delta change table.

In this case, if both the Full Account Aggregation and Delta Aggregation are pointing to the same table, will it cause an error? is it required that they reference different tables?

Thanks!

Hello Sojeong,

I don’t think you can really do it that way. JDBC delta aggregation relies on a change table with identity + action columns, & ISC deletes processed rows from it after each run.

Full & Delta Aggregation SQL can both read from the master table (Delta uses $(identity)), but the “Database Table Name that Contains the Delta Changes” has to be a separate change table, not the master.

Should not creating a readonly view fulfil the requirement in this case?