7/29/2019 Fragmentation in OBIEE

http://slidepdf.com/reader/full/fragmentation-in-obiee 1/9

Fragmentation in OBIEE 

We use fragmentation when we have fact or dimensional data in oneor more different tables or data is splitted in different data sources.

Then each logical table source represents one data segment.

For example, clients, in the first table are clients from A to M, in the

second from M to Z.

Fragmentation of dimension

If our dimensional data is located on two or more physical tables in

database (tables) or it is on separeted data sources then we canhandle this by using UNION ALL views in physical layer.

However for testing this option we'll simulate this by using CHANNELStable. So we splitt it to a table CHANNELS_OTHER and CHANNELS.

Fragmentation attrubur is CHANNEL_ID.

In our SALES fact table that we used here we use CHANNEL_ID fromboth tables CHANNELS and CHANNELS_OTHER.

Physical model, join:

7/29/2019 Fragmentation in OBIEE

http://slidepdf.com/reader/full/fragmentation-in-obiee 2/9

SALES.CHANNEL_ID >- CHANNELS.CHANNEL_IDSALES.CHANNEL_ID >- CHANNELS_OTHER.CHANNEL_ID

BMM:

Settings:

7/29/2019 Fragmentation in OBIEE

http://slidepdf.com/reader/full/fragmentation-in-obiee 3/9

Test in Answers:

Result:

NQQuery.log:

7/29/2019 Fragmentation in OBIEE

http://slidepdf.com/reader/full/fragmentation-in-obiee 4/9

We see that UNION ALL is generated.

If we choose:

NQQuery.log:

We see that the SQL is using only the second fragmented logical tablesource and the condition is applied only for that logical table source.

If we choose:

NQQuery.log:

If we now choose any other attribut (CHANNEL_CLASS) that is not

CHANELL_ID which we used as a fragmentation key:

7/29/2019 Fragmentation in OBIEE

http://slidepdf.com/reader/full/fragmentation-in-obiee 5/9

Then this condition is applied on both logical table sources CHANNEL

and CHANNEL_OTHER:

Fragmentation of fact table

Let's split data for SALES 1998 in separate table SALES_HIST. Data

from 1998 we leave in SALES.

Physical model, join:

SALES.TIME_ID >- TIMES.TIME_ID

SALES_HIST.TIME_ID >- TIMES.TIME_ID

7/29/2019 Fragmentation in OBIEE

http://slidepdf.com/reader/full/fragmentation-in-obiee 6/9

BMM:

Settings (for a fragmentation key we choose CALENDAR_YEAR):

7/29/2019 Fragmentation in OBIEE

http://slidepdf.com/reader/full/fragmentation-in-obiee 7/9

Test in Answers:

Result:

NQQuery.log:

7/29/2019 Fragmentation in OBIEE

http://slidepdf.com/reader/full/fragmentation-in-obiee 8/9

If we choose:

NQQuerylog:

If we choose:

NQQuery.log:

If we now choose any other attribut (CALENDAR_MONTH_DESC) that

is not CALENDAR_YEAR which we used as a fragmentation key:

Then this condition is applied on both logical table sources SALES and

7/29/2019 Fragmentation in OBIEE

http://slidepdf.com/reader/full/fragmentation-in-obiee 9/9

SALES_HIST: