Skip to Content
author's profile photo
Former Member

deltas between DSOs/Cubes/Datasources

Hi

I have few questions regarding delta concept in 7.x and will be thankful if anyone can share their knowledge.

1.If I am extracting data from Oracle database with help of views via DB Connect,is it possible just to have FULL loads or can I have delta loads also?

2.I have a dataflow from DB View datasource to DSO A.This is full load which runs weekly(we delete previous requests from DSO).This DSO is coNnected to another DSO named DSO B.The DTP between DSO A and DSO B has setting 'Delta' as Extraction Mode.The other setting 'Delta Init Extraction From' is choosen as 'Active table(without archive)'....so I assume it extracted full load first time when it was run long back and now it takes only DELTA records from change log of DSO A.How does System determines delta when its between DSO A and DSO B?is it by means of request or timestamp or?where do we make this setting?where do we make settings to determine if its overwrite or additive delta we are using?

3.This DSO B is connecetd to Infocube X through one DTP which has setting Delta as Extraction Mode....and setting for 'Delta Init Extraction From' is chosen as Active table(without archive)...then I assume it loaded Full Load when it was run first time and now it takes deltas only when it is run weekly.It is loaded directly after DSO B is loaded.Where can I find the settings which say if the delta is Additive delta or After Image or Before Image?is delta determined by means of request or timestamp etc?

4.When data is loaded between two DSOs or incase of dataloading between DSO and in infocube,do we use export datasource(named 8XXXX) or we just run DTP....(this dataflow is 7.x)?in which situations do we go for export datasource(named 8xxxxx)?........

Regards.

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • Best Answer
    author's profile photo
    Former Member
    Posted on Mar 06, 2011 at 03:39 PM

    1. You could only load FULL. You could however analyze the possibility of developing a Pseudo delta. For e.g. if you have a date field which gets recorded when the entry is posted to the table, you could develop a pseudo delta mechanism by using a infopackage routine....

    2. The first Delta run between DSO A and DSO B would be treated as a init load. you can see a flag set as init in the DTP monitor header tab. This run takes data based on the setting done in the DTP. In your case the first delta (init) load picks data from the active table and the subsequent delta loads (irrespective of any settings) takes data from the changelog. We need not do any settings to determine the settings for handling these delta loads. By default the DSO overwrites records for the same key. This could be changed by setting the key figures to additive in the tranformation rules. Check the rule for individual key figures. We have an option of setting it as summation.

    3. To a cube the delta always is additive by nature. The DSO changelog below creates after and before images for a changed record or for a new record, it has an 'N' image. These images get aggregated and load to the cube.

    4. In the 7.x flow we do not need export datasources. We load using DTPs.

    The delta in case of DTPs, be it between DSOs or to the cube happens based on request numbers. The data get loaded in the target and the request in the source is marked as loaded (datamart flag).

    Add comment
    10|10000 characters needed characters exceeded