1.3.2 Using Audit Triggers

These triggers should be created after the data conversion is completed and the legacy data for an institution is loaded into the application tables. Otherwise, the internal load of the legacy data into the system inserts rows into the audit tables and the data load process runs slower for tables that have triggers.

Triggers are automatically dropped if the table they are defined on is dropped for any reason. If a table is dropped and then re-created, then the appropriate scripts to create the triggers for that table must be executed again.

An example of such a scenario would be as follows. Using PeopleSoft Application Designer, a field is added to one of the tables on which a trigger is defined. The build action generates an alter script which is executed using a query tool to change the table at the database level. The alter script drops the original table and recreates a new one by the same name. This causes the trigger to be dropped. You must then recreate the trigger for this table. This scenario could occur when an institution makes a modification at their site or applies a fix provided by Oracle that alters such a table. In the case of a fix, the instructions for the fix create a note about recreating the trigger.

These tables and the associated triggers are listed in the next section.