ACID Compliance for Output Write to Oracle Database

[Trevor_Nordberg]

Hello Community,

I'm currently using Alteryx + Server as the batch ETL engine for our data infrastructure. I recently realized that if the output tool is interrupted in the middle of writing to the database, it doesn't roll back the changes, but appears to commit as it writes. This is not ACID compliant, which could become a big problem.

Is this how anyone else understands the tool to work?

Is there a native solution for ACID compliance writes to Oracle database?

I've gotten around this by first writing to tables as a staging layer, and then calling a stored procedure to write to production tables from the staging tables. Some full loads, others incremental loads.

This method works, but I've got to believe Alteryx has a native way of doing this.

Thanks!