Database modeling with entities for history

0

In the system I'm developing there are several parts that will need of data history.

As I did so far, for when I need a history for a table I created another table with the same fields and one more field relating the source table.

So far it's been working fine.

Two problems I have with this approach are:

1) The more tables need history, the more tables I have to replicate, and also need to care for the codes;

2) The data growth for these tables is huge;

What better approaches to this case?

    
asked by anonymous 11.09.2018 / 16:47

0 answers