- Triggers in Rapidi are useful when it is necessary to perform some kind of data manipulation on the data that is about to be transferred or after the data has been transferred.
- This is especially useful if it is not possible to perform the data manipulation with Rapidi, or where, in the context of performance, it is better to use the Data Source itself to do the manipulation.
- Rapidi supports the execution of Triggers before (pre Trigger) it starts to transfer data, and after data has been transferred (post Trigger). There is no support for a per record Trigger.
- Most of the Data Sources that support external programs calling code in the database, calls the code for Stored Procedures.
- If you wish to have Rapidi execute a Trigger, you apply the name of the stored procedure in one of the four fields (i.e. Source Pre Execution, Source Post Execution, Destination Pre Execution or Destination Post Execution) concerning triggers in the requested Transfer.
The order of execution is as follows:
- Source Pre Execution: It is run.
- Source Post Execution: It is run.
- Destination Pre Execution: It is run.
- Destination Post Execution: It is run.
When Pre and Post Triggers are used, the performance of the Transfer is difficult to measure, since it depends on how much time the Triggers spend on the execution.