DSXchange

Hello, We are in the build phase of the large data warehouse project and unfortunately expect a number of model changes. One type of change is the column length being different between sources and the target once source systems start producing data. Since we have not been able to do data profiling, ...

After giving it some more thought I realized one flaw in the scenario I provided. Before Data KEY|ChangeValue P1|ABC123 After Data KEY|ChangeValue|TransactionID P1|DEF123|1 P1|ABC123|2 P1|XYZ789|3 For txn2, we shouldn't be dropping the record as this is valid business change. The change for the Chan...

Welcome aboard. What are you comparing against in the Change Capture stage? How are you ensuring that, for example, txn1 has been committed into that data set when processing txn2? ... Thanks. To answer your question, I am not ensuring txn1 is commited before processing, that's part of the challenge.

We are building a type 2 data warehouse where we expect multiple transactional updates from multiple source systems combined into one file by source system for end of day batch processing. The data architure is such that it is required to maintain each transaction history with the latest transaction...