Currently, I have an entity Ticket, now I plan to create another entity called TicketHistory just as the image shown below to track the changes that happened to Ticket entity, I wonder if this is the "proper" way to design this case ? enter image description here

1 Answer 1


Sure, looks fine.

These kind of history tables are sometimes referred to as temporal tables or temporal data. In fact, some database systems have this as a feature built in, to automatically manage tracking of data changes.

This will vary depending on your database system, but in Microsoft SQL Server these are some of the main data change tracking features available:

  1. Temporal Tables
  2. Change Data Capture (CDC)
  3. Change Tracking
  4. Ledger Tables

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.