Database Driver Considerations

The database driver level implements triggers on the database tables to provide auditing of selected tables, for both changes made through JD Edwards EnterpriseOne database middleware and changes made by third-party software. The auditing includes the recording of signature information when this feature is activated. The auditing information is passed to the drivers from JDB using additional table columns. Database level table triggers generate the auditing information for third-party changes.

The database triggers record auditing information for every INSERT and DELETE statement. For UPDATE statements, the triggers record auditing information only if one or more of the audited columns have a changed data value. Modifying a non-audited column does not generate any audit information.

For a SQL server, a column cannot be dropped if it is:

• A replicated column.

• Used in an index.

• Used in CHECK, FOREIGN KEY, UNIQUE, or PRIMARY KEY constraints.

• Associated with a default defined with the DEFAULT keyword or bound to a default object.

• Bound to a rule.