OBIEE - Fact-based vertical partitioning/fragmentation

Bi Server Architecture With Client

About

This technique allow you to :

It's also known as :

  • Fact-based partitioning
  • Fact partitioning outer join
  • Fact-based fragmentation

You implement it by creating in the Business Model Layer:

  • one logical fact table with two logical tables source for the same level of content
  • two logical fact tables joined with the same logical dimension (known as conforming Dimensions)

When minimum one measure of each logical fact table are included in the query, the BI Server generates two queries for each logical table source and perform a full outer join between them by the dimension columns.

The physical sql issued depends of some database parameters: OBIEE - How to control the use of the WITH CLAUSE and of STITCH Join ?

Reference





Discover More
Bi Server Architecture With Client
OBIEE - (Fragment|ation) (Partitioning)

The fragmentation (known also as partitioning) is the most powerful feature of OBIEE. You can fragment (or partition) any logical table (fact table as dimension table) in more than one logical table source...
Obiee Fact Cross Join
OBIEE - Densification with the fact-based fragmentation capabilities

You may want to view the data in dense form, with rows for all combination of dimension values displayed even when no fact data exist for them. The preservation of the dimensions is is also well known...
Bi Server Architecture With Client
OBIEE - Fact table (of logical fact table)

Dimension tables are expected to store columns that cannot be aggregated whereas fact tables are expected to store measure columns that can be aggregated. As a general rule: don’t include...
Obiee Logical Join Bmm
OBIEE - Full outer Join

To perform a , you have two ways : in the repository by using the fact vertical partitioning capabilities or with the Obiee logical sql To know what sort of join is a full outer join, follow this...
Bi Server Architecture With Client
OBIEE - How to control the use of the WITH CLAUSE and of STITCH Join ?

The physical sql issued when you have designed a vertical fragmentation depend of several database features parameters: PERF_PREFER_MINIMAL_WITH_USAGE: if checked, the WITH clause is not used PERF_PREFER_INTERNAL_STITCH_JOIN:...



Share this page:
Follow us:
Task Runner