The easiest way is to deploy the K2BAudit.CreateAuditTriggersMain procedure and the content of the K2B Audit SQL scripts directory. Then run the procedure making sure the K2B Audit SQL scripts directory is accessible to the program.
Some times developers do not have enough permissions on commands required to create triggers, etc. or they just are not allowed to execute any Data Definition Language code. This is usually the case where Database administrators must perform the task.
The developer should deploy the content of the K2B Audit SQL scripts directory (scripts directory from now on) and the K2BAudit.CreateAuditMetadataMain procedure.
The scripts directory contains a set of script file that let the database administrator handle all triggers. There are scripts for creating, dropping all or selected triggers. There is also a special script (the K2BAuditInitializationCommands.sql script) that creates procedures and functions requiered by triggers. The Database administrator should:
The developer must execute the K2BAudit.CreateAuditMetadataMain main program. It is required as it populates K2B Audit tables with metadata (data about your application). Be sure the K2B Audit SQL scripts directory is accessible to this program.