🚀 Welcome to MDriven Learn –  MDriven is now on Discord!  Don’t miss the latest Release Notes.
Data retention and lifecycle management
This page was created by Wikiadmin on 2026-07-29. Last edited by Wikiadmin on 2026-07-29.

Use this page to distinguish historical-change tracking from preserving complete historical snapshots.

Data retention and history

In MDriven, distinguish between the MDrivenServer History database and database backups:

Need Documented approach
Understand how data reached its current state Use the MDrivenServer History database to track changes and browse data over time from the perspective of the current definition.
Keep a history of model definitions Keep the model in Git or another repository for code and definitions.
Keep full historic snapshots of data and definitions Use database backups and backup-retention settings.

What MDrivenServer History provides

The MDrivenServer History database provides a manageable middle ground for tracking changes and helping users understand the evolution of data from the perspective of the current definition. It can support business, support, debugging, and data-change research.

History is not a history of the model definition. If a new definition is applied, data for that definition cannot be present before the definition was introduced. If a new definition removes an existing definition, historic data that cannot be represented by the current definition is removed over time.

When a history of definitions is required, keep the model definition in Git or another repository for code and definitions. When full historic snapshots of both data and definitions are required, use database backups and backup-retention settings.

Retention and lifecycle considerations

Plan separately for the purpose of each retained record:

  1. Use the History database when users need to investigate changes from the perspective of the current definition.
  2. Keep model definitions in a repository when you need to identify the definition used at an earlier time.
  3. Use database backups and backup-retention settings when you need full historic snapshots of data and definitions.

The supplied documentation states that historic data can be removed over time when it cannot be represented by the current definition.

See also