Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello,
Please see code segment below this script runs for 3days how do I apply Incremental Reload? to reduce the reload time.
[$0FI_C45]:
Load *;
Select PseudoMDX D (
Dimensions (
[0C_CODE] (),
[0G_ACCT] (),
[0FISCYR] ()),
Measures (
[0MEASURES0000000000000000].[0DEBIT0000000000000000000],
[0MEASURES0000000000000000].[0CREDIT000000000000000000]),
From ($0FI_C45));
Store * from [$0FI_C45] into $0FI_C45.QVD;
Drop table [$0FI_C45];
Note: Am using QVOLAPconnector
For incremental loading to work you need to be able to tell which records are new, updated or deleted. Does your olap source contain that information?
Perhaps you should cut out the middle man and use the source data that's used to create the olap cube instead of using the olap cube as source.
I hardly understand what you meant. My data source is SAP BW. Am fetching data from BW cubes (queries). All fields are available. What I need is if I could keep a tab on the data I have already maybe using date on next reload it should start from any new date. I have a field holding date loaded.
I recommend not using a SAP BW cube as data source, but using the original source system as data source instead. If that's not an option and you want to do incremental loading from the BW cube then you need to identify which fields can be used to uniquely identify a record and which field can be used to identify the records that are new or updated.
Yes, I understand. We cant change data source currently. The key field we use to identify new data is the date [FISCALYR] it carries DD/MM/YYYY so how do we make incremental reload from here using the FISCALYR
The easiest way is to make use of the Qlik Components Library: Incremental Load using Qlikview Components | Qlikview Cookbook