<?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 Data modelling issues in QV? in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Data-modelling-issues-in-QV/m-p/568550#M211962</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Guru's,&lt;/P&gt;&lt;P&gt;Please let me know what are the data modelling issues (apart from Synthetic key &amp;amp; Circular reference)&amp;nbsp; faced in QV? &lt;/P&gt;&lt;P&gt;Immediate responses could be appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sree&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 25 Jan 2014 12:44:06 GMT</pubDate>
    <dc:creator />
    <dc:date>2014-01-25T12:44:06Z</dc:date>
    <item>
      <title>Data modelling issues in QV?</title>
      <link>https://community.qlik.com/t5/QlikView/Data-modelling-issues-in-QV/m-p/568550#M211962</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Guru's,&lt;/P&gt;&lt;P&gt;Please let me know what are the data modelling issues (apart from Synthetic key &amp;amp; Circular reference)&amp;nbsp; faced in QV? &lt;/P&gt;&lt;P&gt;Immediate responses could be appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sree&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 25 Jan 2014 12:44:06 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Data-modelling-issues-in-QV/m-p/568550#M211962</guid>
      <dc:creator />
      <dc:date>2014-01-25T12:44:06Z</dc:date>
    </item>
    <item>
      <title>Re: Data modelling issues in QV?</title>
      <link>https://community.qlik.com/t5/QlikView/Data-modelling-issues-in-QV/m-p/568551#M211963</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Always check the Subset Ratios of Joins.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So if you are joining the Product Dimension Table to the Event Table Check the Subset Ratio to have a better Data Model, see below example, the Product Dimension linked to the Product Transactions has a Subset Ratio of 81%, which is not too bad, but ideally you want this at 100%, anything lower the 80% is a concern as you could be holding thousands of products that will have no transaction to select against&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG alt="2014-01-25_1249.png" class="jive-image" src="https://community.qlik.com/legacyfs/online/52087_2014-01-25_1249.png" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 25 Jan 2014 12:54:37 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Data-modelling-issues-in-QV/m-p/568551#M211963</guid>
      <dc:creator>rustyfishbones</dc:creator>
      <dc:date>2014-01-25T12:54:37Z</dc:date>
    </item>
    <item>
      <title>Re: Data modelling issues in QV?</title>
      <link>https://community.qlik.com/t5/QlikView/Data-modelling-issues-in-QV/m-p/568552#M211964</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Another one to look for are tables that only have two fields - using a mapping load to bring the associated data into the parent table is more efficient. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 25 Jan 2014 16:13:02 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Data-modelling-issues-in-QV/m-p/568552#M211964</guid>
      <dc:creator>Colin-Albert</dc:creator>
      <dc:date>2014-01-25T16:13:02Z</dc:date>
    </item>
  </channel>
</rss>

