Transaction Control between normal and aggregated data

[ameet.penkar]

Hi

My requirement is quite unique.

There is a normal table and a aggregated table.

The data for both the tables comes from the same transformer,but before putting the data in the aggregated table,it needs to be aggregated.

Hence the transaction control desired is somnething like this.
1)If any of the Detailed record fails,the associated Summary record should fail

and
2)If the summary record fails,The associated detailed records should fail


Is it possible to achieve this functionality in ETL.If yes,how?

Any info on this would be very useful

[ashwin141]

Hi

Is there any additional constraint for the failure of summarized data or is it the same as molecular data? If it's the same then you can easily implement it in your ETL design by using a transformer and some constraints or stage variables.

Regards
Ashwin

[ameet.penkar]

Hi
The failure of both detailed as well as summarised data is the failure of upsert on the target tables.
Will transaction control be of help in this scenario?

Hi

Is there any additional constraint for the failure of summarized data or is it the same as molecular data? If it's the same then you can easily implement it in your ETL design by using a transformer and some constraints or stage variables.

Regards
Ashwin

[ray.wurlod]

If there's an identifier of the run (such as a date/time updated or a run ID) in each row, you can unwind changes even after they have been committed.