BG_UpdateTimestamp
Applies to
Platform: Microsoft SQL Server · Snowflake · Databricks · Fabric Lakehouse · Fabric Warehouse · Oracle
Architecture: Data Store · Dimensional
BG_UpdateTimestamp holds the load timestamp of the last load that inserted or updated a row. It shows when SCD1 changes overwrote a row, while BG_LoadTimestamp keeps the time of the insert.
Objects that carry it
Store Entity and Entity. Every object of these types gets the term when it is created. The generator calculates the value, so you do not map it; you can change its data type in Manage Default Terms. On Oracle only Store Entities carry it, because Oracle has no Dimensional generator.
Value
The loader writes the load timestamp it receives, the same value as for BG_LoadTimestamp:
- New row: the load timestamp of that load.
- Row updated by an SCD1 change: the load timestamp of the updating load.
BG_LoadTimestampof the row stays unchanged. - Unchanged row: no change.
With SCD2 terms, a change creates a new row, which gets the load timestamp of that load. The unknown-member row has the value 1900-01-01 with default settings.
Data type
| Platform | Type |
|---|---|
| Microsoft SQL Server | datetimeoffset |
| Fabric Warehouse | datetime2(6) |
| Oracle | TIMESTAMP |
| Snowflake | TIMESTAMP_TZ |
| Databricks, Fabric Lakehouse | timestamp |
Example
An Entity with SCD1 terms on Microsoft SQL Server is loaded at 10:00 and at 11:00 UTC. At 11:00 only the customer type of customer 2 changes:
CUSTOMER_ID CUSTOMER_TYPE BG_LoadTimestamp BG_UpdateTimestamp 1 Business 2026-10-27 10:00 2026-10-27 10:00 2 Private 2026-10-27 10:00 2026-10-27 11:00
Related articles
- Reference: BG_LoadTimestamp, BG_RowHashScd1
- See also: Entity, Store Entity