Different type of tables used in Datawarehouse. This is
important to know whoever is working on the data model. Each type of table has
its own set of data.
Following are the different types of tables used in OBIA.
Aggregate tables (_A)
|
Contain summed (aggregated) data.
|
Dimension tables (_D)
|
Star analysis dimensions.
|
Delete tables (_DEL)
|
Tables that store IDs of the entities that were physically
deleted from the source system and should be flagged
as deleted from the data warehouse.
Note that there are two types of delete tables: _DEL
and _PE. For more information about the _PE table
type, see the following Primary extract tables (_PE)
row.
|
Dimension Hierarchy tables (_DH)
|
Tables that store the dimension's
hierarchical structure.
|
Dimension Helper tables (_DHL)
|
Tables that store M:M relationships between two joining
dimension tables.
|
Staging tables for Dimension Helper (_DHLS)
|
Staging tables for storing M:M relationships between two joining
dimension tables.
|
Staging for Dimension Hierarchy (_
DHS)
|
Staging tables for storing the hierarchy structures of dimensions
that have not been through the final extract-transform-load (ETL)
transformations.
|
Staging tables for Dimension (_DS)
|
Tables used to hold dimension information that have not been
through the final ETL transformations.
|
Fact tables (_F)
|
Contain the metrics being analyzed by dimensions.
|
Fact Staging tables (_FS)
|
Staging tables used to hold the metrics being analyzed by
dimensions that have not been through the final ETL transformations.
|
Internal tables (_G, _GS, _S)
|
Internal tables are used primarily by ETL mappings for data
transformation and controlling ETL runs.
|
Helper tables (_H)
|
Helper tables are inserted between the fact and dimension
tables to support a many-to-many (M:M) relationship between fact and
dimension records.
|
Map dimension tables (_M)
|
Tables that store cross-referencing mappings between the
external data ID and the internal ID.
|
Mini dimension tables (_MD)
|
Include combinations of the most queried attributes of their parent
dimensions. The database joins these small tables to the fact tables.
|
Primary extract tables (_PE)
|
Tables that are used to support the soft delete feature.
The table includes all the primary key columns
(integration ID column) from the source system. When a delete
event happens, the full extract from the source compares the data previously
extracted in the primary extract table to determine if a physical deletion
was done in the Siebel application. The soft delete feature is disabled by
default. Therefore, the primary extract tables are not populated until you
enable the soft delete feature.
|
Persisted staging tables (_PS)
|
Tables that source multiple data extracts from the same
source table.
These tables perform some common transformations
required by multiple target objects. They also simplify the
source object to a form that is consumable by the warehouse needed for
multiple target objects. These tables are never truncated during the life of
the data warehouse. These are truncated only during full load, and therefore,
persist the data throughout.
|
Pre-staging temporary table (_TMP)
|
Source-specific tables used as part of the ETL processes to
conform the data to fit the universal staging tables (table types _DS and
_FS). These tables contain intermediate results that are created as part of
the conforming process.
|
Staging tables for Usage Accelerator (_WS)
|
Tables containing the necessary columns for the ETL transformations.
|
No comments:
Post a Comment