<?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: FACT AND DIM TABLE in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/FACT-AND-DIM-TABLE/m-p/2294679#M67532</link>
    <description>Joining tables on Oracle side is probably the best solution to avoid reading unecessary rows from sales table. On other words, rewrite your select query (maybe having a single query to retrieve information from both tables).</description>
    <pubDate>Tue, 07 May 2019 22:15:44 GMT</pubDate>
    <dc:creator>TRF</dc:creator>
    <dc:date>2019-05-07T22:15:44Z</dc:date>
    <item>
      <title>FACT AND DIM TABLE</title>
      <link>https://community.qlik.com/t5/Talend-Studio/FACT-AND-DIM-TABLE/m-p/2294676#M67529</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;
&lt;P&gt;I am new to talend and I am trying to load fact table of daily sales between date range. I am using calendar table which is filter for 2 yrs only&amp;nbsp; and I am joining both tables in tmap&lt;/P&gt;
&lt;P&gt;so when job runs my job reads calendar table lookup first and then it reads the full fact table rather reading just the records between those two date&amp;nbsp;&lt;/P&gt;
&lt;P&gt;any help that how can avoid that so my job only read fact table between calendar date range&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 06 May 2019 22:51:36 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/FACT-AND-DIM-TABLE/m-p/2294676#M67529</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2019-05-06T22:51:36Z</dc:date>
    </item>
    <item>
      <title>Re: FACT AND DIM TABLE</title>
      <link>https://community.qlik.com/t5/Talend-Studio/FACT-AND-DIM-TABLE/m-p/2294677#M67530</link>
      <description>&lt;P&gt;Hello &lt;A href="https://community.qlik.com/s/profile/0053p000007LLbAAAW"&gt;@Ace50&lt;/A&gt; ,&lt;/P&gt; 
&lt;P&gt;Could you please elaborate your case with an example with input and expected output values?&lt;/P&gt; 
&lt;P&gt;Best regards&lt;/P&gt; 
&lt;P&gt;Sabrina&lt;/P&gt;</description>
      <pubDate>Tue, 07 May 2019 03:35:42 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/FACT-AND-DIM-TABLE/m-p/2294677#M67530</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2019-05-07T03:35:42Z</dc:date>
    </item>
    <item>
      <title>Re: FACT AND DIM TABLE</title>
      <link>https://community.qlik.com/t5/Talend-Studio/FACT-AND-DIM-TABLE/m-p/2294678#M67531</link>
      <description>&lt;P&gt;I have a sales fact table and calendar table,please check the attachment, all i want is to filter my fact table with my calendar table as calendar table is filtered for last 3 yrs.&lt;/P&gt;
&lt;P&gt;at the moment my job is reading full fact sale table before filtering and due to this it takes ages&amp;nbsp;&lt;/P&gt;&lt;BR /&gt;&lt;A href="https://community.qlik.com/legacyfs/online/tlnd_dw_files/0683p000009Lv1b"&gt;Capture.PNG&lt;/A&gt;</description>
      <pubDate>Tue, 07 May 2019 16:09:11 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/FACT-AND-DIM-TABLE/m-p/2294678#M67531</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2019-05-07T16:09:11Z</dc:date>
    </item>
    <item>
      <title>Re: FACT AND DIM TABLE</title>
      <link>https://community.qlik.com/t5/Talend-Studio/FACT-AND-DIM-TABLE/m-p/2294679#M67532</link>
      <description>Joining tables on Oracle side is probably the best solution to avoid reading unecessary rows from sales table. On other words, rewrite your select query (maybe having a single query to retrieve information from both tables).</description>
      <pubDate>Tue, 07 May 2019 22:15:44 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/FACT-AND-DIM-TABLE/m-p/2294679#M67532</guid>
      <dc:creator>TRF</dc:creator>
      <dc:date>2019-05-07T22:15:44Z</dc:date>
    </item>
  </channel>
</rss>

