History views past time in the eyes of todays definition

History is not a history of definition - its history of data

If new definition is applied no knowledge of this new definition is available prior to that time - and thus no data can be present prior to this point

If new definition removes existing definition - data that complies to that definition is also removed through out time - this cause data-loss of historic data that cannot be represented in the current definition

To keep history of definition use GIT on the model (or other repository for code/definition)

To keep full historic snapshots of data and definition use database backup -  and backup retention settings

What MDrivenServer-History database offer is a manageable middleground to track changes to help a user understand the evolution of data in the perspective of the current definition. This is a fantastic functionality for mostly stable definitions and help users to see the dynamics of data changes.

Reasons for keeping a history database

1. Answering though questions on how data has ended up in the current state - this is frequently needed for business reasons, support reasons and for debugging reasons
2. Research into data change - how often has data changed historically - how does data grow over time