2/2/2023 0 Comments Timextender history load![]() ![]() It uses the max batch number from the incremental table and the source table, then compares that with the PK table to know if there is updates, if set deletes or new rows. Incremental load method on data source creation levelĮach mapped table in an DWH table has an individual incremental load rule instead of an overarching one. We also have the following guide for how it is set up on the creation level. You can read about these in the following guide. The same applies for deletes from the Business Unit, if the source is not using deletes the DWH can't use it either. Now it is a new table/folder per full load and each load besides that will be added as a batch to that.įor incremental load with updates and/or deletes based on ODX sources, you will need to use updates and/or deletes in the setup, otherwise it will not update the data in the DWH. The change from 20.10.1 is in regards to how data is added from the ODX store. ![]() If you have mapped multiple tables into one DWH table, it will have an individual rule for each. The incremental rule now gets applied on the mapped table. Since the release of TimeXtender version 20.5.1 and again with the 20.10.1, the incremental method has been changed. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |