<?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: Data model design in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Data-model-design/m-p/1168888#M1252241</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Maybe this could give you an input to extend your hierarchy-task:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.qlik.com/qlik-blogpost/4325"&gt;Bill of Materials&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.qlik.com/docs/DOC-3899"&gt;Hierarchy and Hierarchy Belongs to&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Marcus&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 25 Aug 2016 13:15:57 GMT</pubDate>
    <dc:creator>marcus_sommer</dc:creator>
    <dc:date>2016-08-25T13:15:57Z</dc:date>
    <item>
      <title>Data model design</title>
      <link>https://community.qlik.com/t5/QlikView/Data-model-design/m-p/1168885#M1252234</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We have a requirement in our department on what constitutes good data design.&amp;nbsp; I wanted to get some thoughts on one of the required concepts having to do with bridge tables.&amp;nbsp; For example,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A child table has 1,000,000 rows.&amp;nbsp; Each child has exactly one parent but the parent can have many children - classic 1:M.&amp;nbsp; The normal procedure is add ParentID to connect with the parent table but this we're told violates good data modeling.&amp;nbsp; Because the child has&amp;nbsp; data not purely about the child (e.g. product group is related to the product but does describe the product) we're required build a bridge with two fields: ChildID, ParentID.&amp;nbsp; Since there are 1,000,000 child rows, there will be 1,000,000 bridge rows.&amp;nbsp; This would be great if the performance improved but seriously, 1,000,000 x 2 is not going degrade performance?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For me, this is akin to applying normal forms 4 and 5 which even DBA's say creates too many joins and affects performance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BTW, the ID fields are Int32.&amp;nbsp; Hey, at least there not string.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Jan 2026 18:19:17 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Data-model-design/m-p/1168885#M1252234</guid>
      <dc:creator>markp201</dc:creator>
      <dc:date>2026-01-26T18:19:17Z</dc:date>
    </item>
    <item>
      <title>Re: Data model design</title>
      <link>https://community.qlik.com/t5/QlikView/Data-model-design/m-p/1168886#M1252236</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In my openion it's not very helpful to think in normal forms and classical database-structures if you develop datamodels with qlik than qlik worked different and you are developing rather in the opposite direction especially if you handle larger datasets - but there is no general recommendation, it will always depend on the data and the insights which are required which way is more suitable as others. Regarding to your hierarchy-topic might be this useful: &lt;A href="https://community.qlik.com/qlik-blogpost/3433"&gt;Unbalanced, n-level hierarchies&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Marcus&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Aug 2016 07:29:05 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Data-model-design/m-p/1168886#M1252236</guid>
      <dc:creator>marcus_sommer</dc:creator>
      <dc:date>2016-08-25T07:29:05Z</dc:date>
    </item>
    <item>
      <title>Re: Data model design</title>
      <link>https://community.qlik.com/t5/QlikView/Data-model-design/m-p/1168887#M1252238</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As always HIC never fails to share his knowledge but this is the most simple form - a 1-level balanced hierarchy.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Aug 2016 12:24:11 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Data-model-design/m-p/1168887#M1252238</guid>
      <dc:creator>markp201</dc:creator>
      <dc:date>2016-08-25T12:24:11Z</dc:date>
    </item>
    <item>
      <title>Re: Data model design</title>
      <link>https://community.qlik.com/t5/QlikView/Data-model-design/m-p/1168888#M1252241</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Maybe this could give you an input to extend your hierarchy-task:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.qlik.com/qlik-blogpost/4325"&gt;Bill of Materials&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.qlik.com/docs/DOC-3899"&gt;Hierarchy and Hierarchy Belongs to&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Marcus&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Aug 2016 13:15:57 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Data-model-design/m-p/1168888#M1252241</guid>
      <dc:creator>marcus_sommer</dc:creator>
      <dc:date>2016-08-25T13:15:57Z</dc:date>
    </item>
  </channel>
</rss>

