The Historical database tables are divided into two types. They are the static tables that are created at WebSphere® Business Monitor installation time, and the dynamic tables that are created for each imported business measures model.
Column name | Column Type | Column Description | Nullable |
---|---|---|---|
SURROGATE_KEY | INTEGER | This is the primary key | N |
DAY | SMALLINT | Represents the day | N |
MONTH | SMALLINT | Represents the month | N |
YEAR | INTEGER | Represents the year | N |
The Historical database implements a star schema structure with a central Fact table surrounded by multiple Dimension "leaf" tables. The fact table is similar to the context table in the State and Runtime databases. There is one star for the context, and one for the context's corresponding activities. For example, there can be one context instance table, and one activity instance table per context in the State and Runtime databases.
Column name | Column Type | Column Description | Nullable |
---|---|---|---|
MCI_MCIID | DECIMAL(19,0) | Unique identifier of the activity instance and also the primary key of the table. | N |
PARENT_MCIID | DECIMAL(19,0) | Unique identifier of the parent process instance, if any. | Y |
SK_<machine generated name of the dimension> | INTEGER | Foreign key pointing to a dimension table. FK relationship is defined. One of these columns is defined for each dimension present in the context. | Y |
GMT_<machine generated name of metric> | TIMESTAMP | A timestamp value used to store the GMT time value of any timestamp metric data types. (This column is created only when the time metric is marked as a Dimension. When Time metrics are marked as dimensions, they are only stored with day, month, year granularity, so this column provides the ability to see the exact time value of these metrics.) | Y |
The following three column types are used when metrics are marked as Facts (not dimensions).
Column name | Column Type | Column Description | Nullable |
---|---|---|---|
M_<machine generated name> | Data type varies with the data type defined in the business measures model. | Used to represent a metric or Keydefinition value. | Y |
C_<machine generated name> | BIGINT | Used to represent counters. | Y |
T1_<machine generated name> | BIGINT | Used to represent accumulated time for timers. (Timers are represented with a single column in the Historical database; they use multiple columns in the State database.) | Y |
Column name | Column Type | Column Description | Nullable |
---|---|---|---|
SURROGATE_KEY | INTEGER | Machine generated primary key value for this dimension row. PK is defined. | N |
These are the columns that are definition based. The dimension table contains a column for each metric that is defined as part of this dimension.
Column name | Column Type | Column Description | Nullable |
---|---|---|---|
M_<machine generated name> | Data type varies with the data type defined in the business measures model. | Used to represent a metric or key definition value. | Y |
C_<machine generated name> | BIGINT | Used to represent counters. | Y |
T1_<machine generated name> | BIGINT | Used to represent accumulated time for timers. (Timers are represented with a single column in the Historical database, whereas they use multiple columns in the State database). | Y |
The activity star schema follows the same conventions, except that the tables are named AFC_ and ADM_ respectively.