<?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: Alternative approach for Bridge table (for better performance) in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Alternative-approach-for-Bridge-table-for-better-performance/m-p/1056055#M353992</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A href="https://community.qlik.com/message/756728"&gt;Re: link table&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG alt="Capture.JPG" class="jive-image image-1" src="https://community.qlik.com/legacyfs/online/113656_Capture.JPG" style="height: 145px; width: 620px;" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 05 Feb 2016 07:15:12 GMT</pubDate>
    <dc:creator>settu_periasamy</dc:creator>
    <dc:date>2016-02-05T07:15:12Z</dc:date>
    <item>
      <title>Alternative approach for Bridge table (for better performance)</title>
      <link>https://community.qlik.com/t5/QlikView/Alternative-approach-for-Bridge-table-for-better-performance/m-p/1056052#M353989</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Experts,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In my case, I am using &lt;STRONG&gt;"Bridge Table"&lt;/STRONG&gt;.(But it is taking &lt;STRONG&gt;long time&lt;/STRONG&gt; to reload the data model).&lt;/P&gt;&lt;P&gt;Is there any alternative approach ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please suggest to me...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Madhu&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Feb 2016 06:57:00 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Alternative-approach-for-Bridge-table-for-better-performance/m-p/1056052#M353989</guid>
      <dc:creator>madhubabum</dc:creator>
      <dc:date>2016-02-05T06:57:00Z</dc:date>
    </item>
    <item>
      <title>Re: Alternative approach for Bridge table (for better performance)</title>
      <link>https://community.qlik.com/t5/QlikView/Alternative-approach-for-Bridge-table-for-better-performance/m-p/1056053#M353990</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Means link tables , &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With so many Fact tables? Slowly Changing Dimensions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;or &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Date fields more than two, such as canonical Dates .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can your explain example of your Data Model!!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Hirish&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Feb 2016 07:01:48 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Alternative-approach-for-Bridge-table-for-better-performance/m-p/1056053#M353990</guid>
      <dc:creator>HirisH_V7</dc:creator>
      <dc:date>2016-02-05T07:01:48Z</dc:date>
    </item>
    <item>
      <title>Re: Alternative approach for Bridge table (for better performance)</title>
      <link>https://community.qlik.com/t5/QlikView/Alternative-approach-for-Bridge-table-for-better-performance/m-p/1056054#M353991</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Bridge Tables? &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Feb 2016 07:09:10 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Alternative-approach-for-Bridge-table-for-better-performance/m-p/1056054#M353991</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2016-02-05T07:09:10Z</dc:date>
    </item>
    <item>
      <title>Re: Alternative approach for Bridge table (for better performance)</title>
      <link>https://community.qlik.com/t5/QlikView/Alternative-approach-for-Bridge-table-for-better-performance/m-p/1056055#M353992</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A href="https://community.qlik.com/message/756728"&gt;Re: link table&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG alt="Capture.JPG" class="jive-image image-1" src="https://community.qlik.com/legacyfs/online/113656_Capture.JPG" style="height: 145px; width: 620px;" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Feb 2016 07:15:12 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Alternative-approach-for-Bridge-table-for-better-performance/m-p/1056055#M353992</guid>
      <dc:creator>settu_periasamy</dc:creator>
      <dc:date>2016-02-05T07:15:12Z</dc:date>
    </item>
    <item>
      <title>Re: Alternative approach for Bridge table (for better performance)</title>
      <link>https://community.qlik.com/t5/QlikView/Alternative-approach-for-Bridge-table-for-better-performance/m-p/1056056#M353993</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Try Concatenate in your scenario. All fields take into one table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Feb 2016 07:44:29 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Alternative-approach-for-Bridge-table-for-better-performance/m-p/1056056#M353993</guid>
      <dc:creator>mithilesh17</dc:creator>
      <dc:date>2016-02-05T07:44:29Z</dc:date>
    </item>
    <item>
      <title>Re: Alternative approach for Bridge table (for better performance)</title>
      <link>https://community.qlik.com/t5/QlikView/Alternative-approach-for-Bridge-table-for-better-performance/m-p/1056057#M353994</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HI,&lt;/P&gt;&lt;P&gt;Attach some sample data so that it would be easier to suggest the solution, otherwise it is difficult.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Jagan.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Feb 2016 07:59:15 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Alternative-approach-for-Bridge-table-for-better-performance/m-p/1056057#M353994</guid>
      <dc:creator>jagan</dc:creator>
      <dc:date>2016-02-05T07:59:15Z</dc:date>
    </item>
    <item>
      <title>Re: Alternative approach for Bridge table (for better performance)</title>
      <link>https://community.qlik.com/t5/QlikView/Alternative-approach-for-Bridge-table-for-better-performance/m-p/2003354#M1221461</link>
      <description>&lt;P&gt;Bridge table isn't the problem, it depends on how your script your data load&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 11 Nov 2022 05:38:33 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Alternative-approach-for-Bridge-table-for-better-performance/m-p/2003354#M1221461</guid>
      <dc:creator>vinieme12</dc:creator>
      <dc:date>2022-11-11T05:38:33Z</dc:date>
    </item>
  </channel>
</rss>

