Transactional databases and job rollback
This section describes ways to make databases transactional and implement job rollback.
By default, when you run a PDI job or transformation that makes changes to a database table, those changes are committed as the transformation or job executes. Sometimes, this can cause an issue if a job or transformation fails. For example, if you run a job that updates then syncs two tables, but the job fails before you can write to the second table, the first table might be updated and the other might not, rendering them both out of sync. If this is a concern, consider implementing job rollback by making the transformation or job databases (or both) transactional. When you do this, changes to a data source occur only if a transformation or job completes successfully. Otherwise, the information in both data sources remain unchanged.
The following sections provide procedural information on how to make databases transactional. The wiki provides more detail.
Make a transformation database transactional
Procedure
In the PDI client, open a transformation.
Right-click the transformation canvas and select Properties from the menu that appears.
Click the Miscellaneous tab.
Select the Make the transformation database transactional checkbox.
Click OK to close the window.
Make a job database transactional
Procedure
In PDI client, open a job.
Right-click in the job canvas and select Properties from the menu that appears.
Click the Transactions tab.
Select the Make the job database transactional checkbox.
Click OK to close the window.