Audit columns and triggers are automatically added to objects the first time they are imported into OneData. When database changes are made in source system, like re-creating the table for changing column order after the object has been brought into OneData, these columns or triggers may be dropped. Therefore, after these actions are performed, it is important to verify that the audit columns and triggers exist as described in the table below.

Every table and view represented as a OneData object must have audit columns and triggers. For tables, OneData automatically creates both audit columns and triggers when the table is created or imported into OneData. For logical objects, such as views, OneData does not define triggers or columns. Therefore, you must manually create audit columns in the source before importing the view into OneData.

The following audit columns must exist in all tables and views in both the staging area and the production data.