Thank you, this was very helpful, i am working in an scenario where i have interval dates but two changing dimensions, this was useful to understand what i'm gonna do.
Very helpful. Thank you.How do we implement a scenario where we don't have interval dates? For example, I have a Sales fact table and Customer dimension that changes by name field. How could this be implemented or do you have a different scenario for this?Cheers!
I think in such scenario we need to some sort of tagging or separate field which can keep track of changes and mapped to the latest record. In this way with the help of the latest record, you can always get the old values from the table.
Completely understood the concept but then 2 fields are being matched between both the tables causing a synthetic key, so how do I remove the synthetic key?
Thank you, this was very helpful, i am working in an scenario where i have interval dates but two changing dimensions, this was useful to understand what i'm gonna do.
Very helpful. Thank you.How do we implement a scenario where we don't have interval dates? For example, I have a Sales fact table and Customer dimension that changes by name field. How could this be implemented or do you have a different scenario for this?Cheers!
I think in such scenario we need to some sort of tagging or separate field which can keep track of changes and mapped to the latest record. In this way with the help of the latest record, you can always get the old values from the table.
Try with wildmatch() function in IntervalMatch. Abhishek correct me if I'm wrong.
Completely understood the concept but then 2 fields are being matched between both the tables causing a synthetic key, so how do I remove the synthetic key?
plz can you share code and data