We like to say that Ajilius is driven by our users, and here is another example.
Release 2.2.16, due Sunday, will include a feature to reset incremental loads, allowing a load to be rerun even after it succeeds. One driver for this feature is detection of a source system error that does not affect the running of a load, but does affect the data content of the load.
The “ajilius” schema of your data warehouse contains a table named “ajilius_control”. This table holds one row for each column for which incremental values are tracked. We have modified this table to include a “previous” and “latest” value.
On successfully processing a load, we update the “previous” value with the contents of the “latest” value (that was used to process the load), and over-write the “latest” value with the maximum column value from the load.
Now, you can select a menu option Schedule | Reset Controls:
On selecting this option, you will be shown a screen listing all tables for which incremental controls have been defined:
When you press the Reset button, the control values of any checked table will be reset to their previous state. This enables the incremental load to be repeated.
Ajilius. Tipping the hat to Steve 😉