<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: What should I use to Populate the fact table! in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/What-should-I-use-to-Populate-the-fact-table/m-p/2316585#M87118</link>
    <description>Hi hayane,
&lt;BR /&gt;I think you really need to be clear about the process you want to implement and your information model.
&lt;BR /&gt;I guess you plan to fill your dimension table first, then your fact table with a foreign key referencing your dimension table. To do that, you need to know which key to use : how do you link a fact to it's dimension ? When this is clear, you will have to implement it. There comes Talend.
&lt;BR /&gt;Let's assume I want to move data from a source to a datawarehouse. I can use a "corresondance file" to keep the link between my dimension data from the source, and my dimension data in the dimension table of the datawarehouse. Then, I link the fact data from the source to its related dimension data from the source, and using the correspondance file, i can trace the corresponding data in the datawarehouse. This is how I get the foreign key I need to populate my fact table.
&lt;BR /&gt;The components involved in this job are tmysqlinput, tmysqlInput, tFileInputDelimited all connected to a tmap, of which the output is linked to a tmysqlOutput.
&lt;BR /&gt;I fill my dimension table first, by runing the job (the one you've already made), and then I run the new job designed to fill the fact table.
&lt;BR /&gt;Good luck</description>
    <pubDate>Tue, 08 Sep 2009 09:54:18 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2009-09-08T09:54:18Z</dc:date>
    <item>
      <title>What should I use to Populate the fact table!</title>
      <link>https://community.qlik.com/t5/Talend-Studio/What-should-I-use-to-Populate-the-fact-table/m-p/2316583#M87116</link>
      <description>Hi everybody !&lt;BR /&gt;I create my dimension table with Mysqlconnection, tmysqlinput, tmap and tmysqlSCD in a job.Now, to populate the fact table I create another job .How can i do this and link the compenent?Except tAggregateRow what should I use ? should I call the dimension tables?or tables in relationel database and how much compenents ?&lt;BR /&gt;Im sorry but I'm a little confused :s&lt;BR /&gt;&lt;BR /&gt;Thanks in advance</description>
      <pubDate>Sat, 16 Nov 2024 13:47:00 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/What-should-I-use-to-Populate-the-fact-table/m-p/2316583#M87116</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2024-11-16T13:47:00Z</dc:date>
    </item>
    <item>
      <title>Re: What should I use to Populate the fact table!</title>
      <link>https://community.qlik.com/t5/Talend-Studio/What-should-I-use-to-Populate-the-fact-table/m-p/2316584#M87117</link>
      <description>Hello 
&lt;BR /&gt;To call another job, you can use the tRunJob component.(see user documentation to know its usage) and you pass the relevant parameter to another job via tRunJob. see a 1654 
&lt;BR /&gt;Best regards 
&lt;BR /&gt; 
&lt;BR /&gt; shong</description>
      <pubDate>Tue, 08 Sep 2009 04:59:03 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/What-should-I-use-to-Populate-the-fact-table/m-p/2316584#M87117</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2009-09-08T04:59:03Z</dc:date>
    </item>
    <item>
      <title>Re: What should I use to Populate the fact table!</title>
      <link>https://community.qlik.com/t5/Talend-Studio/What-should-I-use-to-Populate-the-fact-table/m-p/2316585#M87118</link>
      <description>Hi hayane,
&lt;BR /&gt;I think you really need to be clear about the process you want to implement and your information model.
&lt;BR /&gt;I guess you plan to fill your dimension table first, then your fact table with a foreign key referencing your dimension table. To do that, you need to know which key to use : how do you link a fact to it's dimension ? When this is clear, you will have to implement it. There comes Talend.
&lt;BR /&gt;Let's assume I want to move data from a source to a datawarehouse. I can use a "corresondance file" to keep the link between my dimension data from the source, and my dimension data in the dimension table of the datawarehouse. Then, I link the fact data from the source to its related dimension data from the source, and using the correspondance file, i can trace the corresponding data in the datawarehouse. This is how I get the foreign key I need to populate my fact table.
&lt;BR /&gt;The components involved in this job are tmysqlinput, tmysqlInput, tFileInputDelimited all connected to a tmap, of which the output is linked to a tmysqlOutput.
&lt;BR /&gt;I fill my dimension table first, by runing the job (the one you've already made), and then I run the new job designed to fill the fact table.
&lt;BR /&gt;Good luck</description>
      <pubDate>Tue, 08 Sep 2009 09:54:18 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/What-should-I-use-to-Populate-the-fact-table/m-p/2316585#M87118</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2009-09-08T09:54:18Z</dc:date>
    </item>
  </channel>
</rss>

