Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable
‎2016-11-22 04:48 AM

Which would be better option to handle Historization in Talend tool

Hi,
I am trying to implement Data warehouse using Talend 6.21. I have implemented Historization using SCD components. Wanted to know whether implementation of SCD using components available in talend is a better option or creating a job using tmap and other components to handle is better. Please suggest and Is their any impact from future Talend releases and with respect to performance as well.
Labels (2)
Labels
326 Views
0 Likes
2 Replies
Anonymous
Not applicable
‎2016-11-22 10:54 PM
Author

Hi,
Usually, we use tXXXSCD component to  address Slowly Changing Dimension needs, read regularly a source of data and logging the changes into a dedicated SCD table.
For your  Historization requirement, could you please elaborate your case with an example with input and expected output values?
Best regards
Sabrina
326 Views
0 Likes
Anonymous
Not applicable
‎2016-11-23 01:51 AM
Author

Thank you for your input. 
I am implementing SCD Type 1 and SCD Type 2.
Exmaple for SCD Type 1 one:
Input table: Product
0683p000009MBrB.png
Example for SCD Type 2
0683p000009MCGJ.png
So for these scenarios can you let me know will there be any difference inn performance between SCD component  and manual(by using tmap and other components).
326 Views
0 Likes