Incremental Load

[#1]

Hi all,

can anybody clear my doubt on Incremental load with "Insert ,Update and Delete" concept, i have done all the concepts of incremental load (Insert only,Insert and Update,Insert ,Update and delete)

I have followed these steps to complete this

Process1:

1.Loading initial data into the qlikview app

2.storing data into QVD file

3.Finding max date from the existing QVD (on initial data)

4.fetching data from data source on max date

5.concatenating new records with existing records

6.finally updating QVD with all records

for Delete,

i have added the below step

7. performed Inner join on the actual data source with updated QVD.

so it has completed my task end to end for "Insert,Update and Delete" functionality.

but, i have raised with a doubt in myself that , why we need to follow step by step as described above to fetch (New ,Updated and Deleted) data into the QVD.

can't we go with the below steps instead of following all 7 steps :

Process 2:

1.Loading initial data into the qlikview app

7. performed Inner join on the actual data source with either from QVD/Initial data source.

Is there any difference would be done from Process 1 to Process 2

Thank you,

Charitha.

[SunilChauhan]

Process 2 can be for DElete  not for insert and update.

beacuse inner join take matches from first and second  Tables.it will find common records based out key field

hope this helps

[#3]

Yes, for Delete only, we can go with Process 2 than Process 1.but i have doubt that is there any difference

Thanks

charitha

[SunilChauhan]

but how to achieve table which you are suppose to do inner join with initial or historical data???

[SunilChauhan]

i mean to say here is to achive data after deletion of record( for new Data)

you need to follow those steps but condition is not on Max date .its based on primary key.

hope this helps

[#6]

Hi Lakshmi,

In Process 2, step 1 must be full Load other wise you can't insert & update the records. So its full load, there is no Incremental load.

You can follow any method, but finally we can end up with only one method based on Reload time factor.