Skip to content
Contact us Go to Customer Portal
  • There are no suggestions because the search field is empty.

BG_ValidFromTimestamp

Applies to
Platform: Microsoft SQL Server · Snowflake · Snowflake dbt · Databricks · Databricks dbt · Fabric Lakehouse · Fabric Warehouse · Oracle
Architecture: Data Store · Data Vault · Dimensional · Data Mart

BG_ValidFromTimestamp is the Default Term that holds the start of the validity of a row version in a historized model object. Together with BG_ValidToTimestamp it gives the period in which the version was current.

Objects that carry it

  • Store Entity, Entity and Mart Dimension
  • Every satellite type of the Raw Vault and the Business Vault
  • PIT, Business PIT, History View and Business History View

Stage objects do not carry it.

Data type

PlatformType
Microsoft SQL ServerDATETIMEOFFSET (precision 7)
Snowflake, Snowflake dbtTIMESTAMP_TZ
Databricks, Databricks dbt, Fabric LakehouseTIMESTAMP
Fabric WarehouseDATETIME2(6)
OracleTIMESTAMP

Value

  • Satellites: the load timestamp of the load that inserted the version, the same value as BG_LoadTimestamp.
  • Store Entity and Entity: the first version of a new business key gets Begin of Universe. Every later version gets the load timestamp.
  • Multi-version load and Mart Dimension with a historized source: the value of the Version Valid From Term. A NULL value becomes Begin of Universe.
  • Unknown-member rows: Begin of Universe.

Map a source value

On a Store Entity or an Entity you can map BG_ValidFromTimestamp in Manage Term Mappings. The first version of a new business key then gets the mapped value, and a NULL value becomes Begin of Universe. Other model object types do not offer the mapping. Available since Generator 2.2.

Validation warns about a mapping that has no effect:

  • ID-10057: no term or relationship of the model object has Historization Type SCD2, so it is not historized.
  • ID-10058: the Store Entity also has a Version Valid From Term. The multi-version load uses that term, and the mapping is ignored.

Example

A Store Entity on Microsoft SQL Server is loaded at 10:00 and at 11:00 UTC. In the second load, customer 1 has a new address and customer 3 is new. The table then holds:

CUSTOMER_ID  ADDRESS_LINE1   BG_ValidFromTimestamp
1            Main Street 1   1900-01-01 00:00 +00:00
1            Main Street 3   2026-10-27 11:00 +00:00
2            Station Road 5  1900-01-01 00:00 +00:00
3            Lake Road 7     1900-01-01 00:00 +00:00

Customer 3 starts at Begin of Universe although it was loaded at 11:00, because it is the first version of its key.

Related articles