I've have a question about modelling the Audit Logs that are stored in our Source Application. The source application is used to store Tickets. Most of the information of a Ticket is stored in the table inquiry. Next to the inquiry table there is an inquiry_audit table.
The audit table stores changes
that were made to an inquiry. The structure of the table:
audit_id | action_date | inquiry_id | action | old_value | new_value
1 | 2015-11-25 10:13 | 23 | status | new | closed
1 | 2015-11-25 10:13 | 23 | prio | high | low
The idea was to store these records as a satellite
of the h_ticket. For this satellite
having an load_end_date
is a bit
diffecult. Is it ok to leave this column out of the satellite
or should we model the audit log differently? Maybe look into multi active satellites
I'm curious about your opinions.