<?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: When does one pick a snowflake model over joining redundant data in the data load editor? in App Development</title>
    <link>https://community.qlik.com/t5/App-Development/When-does-one-pick-a-snowflake-model-over-joining-redundant-data/m-p/2064886#M87345</link>
    <description>&lt;P&gt;That data are&amp;nbsp;redundant is usually not a problem within Qlik because only distinct values are stored within the system-table (for each field one) and connected with a bit-stuffed index to the data-tables - at least from storing/performance point of view. How suitable the relation-ship between tables fits to the view requirements is a different matter and couldn't be said in general. It always depends ...&lt;/P&gt;
&lt;P&gt;Beside this it's often helpful to specialize the applications. This could mean to create a sales-analysis with just a few stock-information and creating a stock-analysis which contains the sales as one part of the product-movements but not trying to combine complex analysis from various areas.&lt;/P&gt;</description>
    <pubDate>Wed, 26 Apr 2023 14:42:29 GMT</pubDate>
    <dc:creator>marcus_sommer</dc:creator>
    <dc:date>2023-04-26T14:42:29Z</dc:date>
    <item>
      <title>When does one pick a snowflake model over joining redundant data in the data load editor?</title>
      <link>https://community.qlik.com/t5/App-Development/When-does-one-pick-a-snowflake-model-over-joining-redundant-data/m-p/2064879#M87343</link>
      <description>&lt;P&gt;At what point would one consider joining redundant data onto a dimension table over a snowflake model?&lt;/P&gt;
&lt;P&gt;Let's say we have a sales table, this sales table has a product table with product ID, description, product status and warehouse ID.&lt;/P&gt;
&lt;TABLE border="1" width="100%"&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD width="33.333333333333336%"&gt;Product ID&lt;/TD&gt;
&lt;TD width="33.333333333333336%"&gt;Description&lt;/TD&gt;
&lt;TD width="16.666666666666668%"&gt;Product Status&lt;/TD&gt;
&lt;TD width="16.666666666666668%"&gt;Warehouse ID&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="33.333333333333336%"&gt;0001&lt;/TD&gt;
&lt;TD width="33.333333333333336%"&gt;Bottle of water&lt;/TD&gt;
&lt;TD width="16.666666666666668%"&gt;Available&lt;/TD&gt;
&lt;TD width="16.666666666666668%"&gt;w1&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This bottle of water also has a warehouse connected to it.&lt;/P&gt;
&lt;TABLE border="1" width="100%"&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD width="25%" height="25px"&gt;Warehouse ID&lt;/TD&gt;
&lt;TD width="25%" height="25px"&gt;Warehouse Location&lt;/TD&gt;
&lt;TD width="25%" height="25px"&gt;Warehouse Shelf&lt;/TD&gt;
&lt;TD width="25%" height="25px"&gt;Warehouse Category&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="25%" height="25px"&gt;w1&lt;/TD&gt;
&lt;TD width="25%" height="25px"&gt;France&lt;/TD&gt;
&lt;TD width="25%" height="25px"&gt;111&lt;/TD&gt;
&lt;TD width="25%" height="25px"&gt;Consumables&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;At what point would you no longer join warehouse to product table as one warehouse could contain hundreds of products and in turn create a lot of duplicate data. As I understand Qlik will have to calculate this join whenever you're using it on the front. &lt;STRONG&gt;However does this mean we always pre-join such things or is there a point where we'd not do this?&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Should we instead add the Product ID to the warehouse table and connect it directly to the sales table?&lt;/P&gt;</description>
      <pubDate>Wed, 26 Apr 2023 14:17:08 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/When-does-one-pick-a-snowflake-model-over-joining-redundant-data/m-p/2064879#M87343</guid>
      <dc:creator>ThePewSpecialist</dc:creator>
      <dc:date>2023-04-26T14:17:08Z</dc:date>
    </item>
    <item>
      <title>Re: When does one pick a snowflake model over joining redundant data in the data load editor?</title>
      <link>https://community.qlik.com/t5/App-Development/When-does-one-pick-a-snowflake-model-over-joining-redundant-data/m-p/2064886#M87345</link>
      <description>&lt;P&gt;That data are&amp;nbsp;redundant is usually not a problem within Qlik because only distinct values are stored within the system-table (for each field one) and connected with a bit-stuffed index to the data-tables - at least from storing/performance point of view. How suitable the relation-ship between tables fits to the view requirements is a different matter and couldn't be said in general. It always depends ...&lt;/P&gt;
&lt;P&gt;Beside this it's often helpful to specialize the applications. This could mean to create a sales-analysis with just a few stock-information and creating a stock-analysis which contains the sales as one part of the product-movements but not trying to combine complex analysis from various areas.&lt;/P&gt;</description>
      <pubDate>Wed, 26 Apr 2023 14:42:29 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/When-does-one-pick-a-snowflake-model-over-joining-redundant-data/m-p/2064886#M87345</guid>
      <dc:creator>marcus_sommer</dc:creator>
      <dc:date>2023-04-26T14:42:29Z</dc:date>
    </item>
  </channel>
</rss>

