Hi alevy,

Thank you for your reply.

I can try what you suggest, but wouldn't that only work to roll back the insert that failed?  What about other inserts that were successful, but that should then be rolled back because of the failure?  Sort of like setting up a transaction.

Thanks,
Nathan

Hi shong,

I actually don't have the job set up yet so I can't take a screenshot of anything.

To answer your question though, in my example, if the parent record gets inserted successfully and the child records fail, I'd like both the parent and child records to be rolled back.  Essentially, the each parent and associated child record insert is a "transaction."

Thanks,
Nathan

In the connection component, uncheck "auto commit".  Nothing will be committed until you use a commit component and everything since last commit will be rolled back if you use a rollback component.  If you have multiple parents you need to commit each parent and child(ren) group separately.  Have a go and put up some screenprints and sample data if you have a problem.

If the job were exported as a war file, deployed to a server, and called via java classes, would turning off and on auto commit on the java connection also be a viable solution? Any idea on performance hit when committing such a small batch. Throughput is excellent for large
batches.