Optimize 10.5 | webMethods Optimize Documentation | Administering webMethods Optimize | Optimize Schema | Fact Tables (BAM_FACT_<Event Map Name>_V1)
 
Fact Tables (BAM_FACT_<Event Map Name>_V1)
Fact tables capture information for every event (that has an event map) generated for Optimize. Each Fact table is associated with one event map and is created after the event map is saved through the Optimize interface in My webMethods. The name of the table is derived from the event map name (not the internal name).
The following table describes the columns in the Fact tables.
Column and Description
BAM_FACT <Event Map Name>_V1_ID
Primary key that uniquely identifies an event row.
<Fact Name>_FACT
Fact columns contain measurable values from events. Usually, though not always, this is a number. There can be any number of fact columns. Examples include order amount, transaction count, and failure percentage.
<Transaction Name>_TXN
Transaction columns contain textual information about an event that is not measurable and not a dimension. Examples include order number, transaction date, and phone number. Optimize does not use this information; it is collected solely for potential use by a reporting tool.
<Dimension Name>_DIM
Dimension columns contain integer values that are foreign keys to dimension tables. Associated dimension tables contain more information related to these dimension foreign keys.
DG_WAREHOUSE_DATE_DIM_ID
This column contains information about the date an event occurred, rather than when it was inserted into the database. The column value is a foreign key reference to the DG_WAREHOUSE_DATE_DIM table, which contains different representations of the date value.
DG_WAREHOUSE_TIME_DIM_ID
This column contains information about the time an event occurred, rather than when it was inserted into the database. The column value is a foreign key reference to the DG_WAREHOUSE_TIME_DIM table, which contains different representations of the time value.
CTRL_INSERT_DT
This is the date and time when an event was inserted into the database. If events from several days ago were delayed and entered today, the CTRL_INSERT_DT value would be today, but the DATE_DIM_ID and TIME_DIM_ID (see above), would be from several days ago. Optimize does not use this field.