Release note - beVault 3.8

We are thrilled to announce the release of beVault 3.8, bringing significant enhancements to our data vault automation tool. This version focuses on bringing back the multi-active satellites into beVault.

Check out this release note to see what’s new and stay tuned for new incoming releases in 2025 🚀

Multi-active satellites

beVault 3.8 introduces first-class support for multi-active satellites (MAS). MAS are used when a single business key (hash key) legitimately has multiple concurrent attribute records at a given point in time (for example: multiple phone numbers, addresses, or contact methods for the same customer).

Two multi-active satellite loading strategies are available:

1) Standard (Data Vault Alliance–recommended)

• Behavior

  • On every load, all records for a given hash key are inserted into the satellite.

  • This guarantees that the complete set for a hash key is captured per load cycle, preserving the source order and enabling deterministic rebuilds of the source set.

• Why this approach

  • Simplicity and auditability: each load is a full snapshot of the multi-active set.

  • Reproducibility: you can rebuild the source set in the same order for a given hash key.

• Trade-offs

  • Higher write volumes and storage, since unchanged records are reinserted each load.

  • Straightforward lineage and recovery.

2) Delta-driven

• Behavior

  • For each hash key, beVault computes a hashdiff over the entire ordered set of records.

  • Only if at least one record in the set changes does beVault load the new set for that hash key.

  • You define a sequence key to establish a deterministic order of the records in the set; this ensures the hashdiff is stable and comparable across loads.

• Why this approach

  • Efficiency: reduces unnecessary inserts when multi-active sets are unchanged.

• Trade-offs

  • Requires careful definition of the sequence key to guarantee stable ordering.

  • Additional compute to build an ordered-set hashdiff; lower storage/write volume overall.

Choosing a strategy

• Pick Standard when:

  • You prioritize simplicity, auditability, and guaranteed reproducibility of the source set (as per Data Vault Alliance guidance).

  • The multi-active sets are small or change frequently enough that full reloads are acceptable.

• Pick Delta-driven when:

  • You want to minimize load volumes for large multi-active sets that change infrequently.

  • You can provide a robust, deterministic sequence key to order the set consistently.

Impact and known limitations (3.8)

• No computed Load End Date view

  • Multi-active satellites currently don’t provide a view with a computed load end date like descriptive satellites.

• Not included in PIT tables

  • PIT (Point-In-Time) tables do not yet incorporate multi-active satellites.

• No data quality controls

  • It is not currently possible to create data quality controls on multi-active satellites.

These limitations are expected to be addressed in future releases.

List of changes

• Multi-active satellite

  • Add the possibility to create standard multi-active satellites in the Source module.

  • Add the possibility to create delta-driven multi-active satellites in the Source module with a sequence column.

  • Add a new icon to identify multi-active satellites.

• The download of the script while deploying a version now contains the loading queries (DML) as well

• Snowflake support - add support for public/private key pair authentication

• Distribute - snapshot group is not mandatory for the scripts anymore

• States - Change executions' names to better identify them.

• Errors happening while executing a query in a database will now display the error message coming from the database instead of a generic message

• UX/UI improvements & bug fixing

  • Migration of metavault’s UI to Angular 19

Components' version

Fix Versions