dv-bv-activity-schema

Mapping raw events into named activities for Data Vault satellites requires consolidating raw vault data into a standardized BV non-historised satellite with fixed column sets and per-activity Dynamic Tables for analytics consumption.

An Activity Schema satellite standardizes how events are interpreted and stored in DVOS, enabling consistent BI consumption and auditing when you need to stream raw vault events into fixed-column analytics structures.

Deploying a non-historised satellite in DVOS involves configuring streaming tasks to populate the SAT_BV_NH_{ENTITY}_STREAM table, requiring explicit entity mapping and authoritative attributes per activity to populate fixed columns and ghost records.

Yes, Activity Schema BV satellite design requires explicit entity mapping and authoritative attributes per activity to correctly configure the staging views and streaming tasks that populate the non-historised satellite tables.

Standardizing BI consumption from Raw Vault events is best achieved by implementing a BV satellite with fixed column sets, staging views, and per-activity Dynamic Tables to ensure consistent event interpretation and auditing.

Ghost records and fixed columns in a SAT_BV_NH entity stream provide standardized structural integrity for the Activity Schema, ensuring consistent analytics consumption and auditing across all mapped raw vault activities.