<?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 Multiple Dimension Tables linked to Fact table using same key field in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Multiple-Dimension-Tables-linked-to-Fact-table-using-same-key/m-p/1703025#M592330</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Question on data model design.&lt;/P&gt;&lt;P&gt;I have three tables.&amp;nbsp; Fact table being production events.&amp;nbsp; Two dimension tables - Job_Master that has one record per Job and fields such as Plant, Ordered Qty, Due Date etc.&amp;nbsp; Job_Customer is a list of customers that have used product from that Job.&amp;nbsp; There can be multiple customers per Job.&amp;nbsp; &amp;nbsp;The three tables all link with a key field %Job.&lt;/P&gt;&lt;P&gt;I choose to have both dimension tables connect using %Job field to Fact rather than using a snowflake schema of linking the Fact to Job Master and then Job Master to Job_Customer.&amp;nbsp; I can't combine them to one dimension table as that would replicate the Job_Master details for each customer.&lt;/P&gt;&lt;P&gt;This works, but am curious if there are any known downsides, particularly in performance for front-end calculation.&amp;nbsp; Should I be avoiding this design and instead using snowflake, or possible two separate key fields to join the tables.&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;&lt;P&gt;Michael&lt;/P&gt;</description>
    <pubDate>Sat, 16 Nov 2024 18:37:39 GMT</pubDate>
    <dc:creator>michael_anthony</dc:creator>
    <dc:date>2024-11-16T18:37:39Z</dc:date>
    <item>
      <title>Multiple Dimension Tables linked to Fact table using same key field</title>
      <link>https://community.qlik.com/t5/QlikView/Multiple-Dimension-Tables-linked-to-Fact-table-using-same-key/m-p/1703025#M592330</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Question on data model design.&lt;/P&gt;&lt;P&gt;I have three tables.&amp;nbsp; Fact table being production events.&amp;nbsp; Two dimension tables - Job_Master that has one record per Job and fields such as Plant, Ordered Qty, Due Date etc.&amp;nbsp; Job_Customer is a list of customers that have used product from that Job.&amp;nbsp; There can be multiple customers per Job.&amp;nbsp; &amp;nbsp;The three tables all link with a key field %Job.&lt;/P&gt;&lt;P&gt;I choose to have both dimension tables connect using %Job field to Fact rather than using a snowflake schema of linking the Fact to Job Master and then Job Master to Job_Customer.&amp;nbsp; I can't combine them to one dimension table as that would replicate the Job_Master details for each customer.&lt;/P&gt;&lt;P&gt;This works, but am curious if there are any known downsides, particularly in performance for front-end calculation.&amp;nbsp; Should I be avoiding this design and instead using snowflake, or possible two separate key fields to join the tables.&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;&lt;P&gt;Michael&lt;/P&gt;</description>
      <pubDate>Sat, 16 Nov 2024 18:37:39 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Multiple-Dimension-Tables-linked-to-Fact-table-using-same-key/m-p/1703025#M592330</guid>
      <dc:creator>michael_anthony</dc:creator>
      <dc:date>2024-11-16T18:37:39Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple Dimension Tables linked to Fact table using same key field</title>
      <link>https://community.qlik.com/t5/QlikView/Multiple-Dimension-Tables-linked-to-Fact-table-using-same-key/m-p/1718029#M592331</link>
      <description>&lt;P&gt;I would recommend the following two links:&lt;/P&gt;&lt;P&gt;&lt;A href="https://help.qlik.com/en-US/qlikview/April2020/Subsystems/Client/Content/QV_QlikView/LoadData/best-practices-data-modeling.htm" target="_blank" rel="noopener"&gt;https://help.qlik.com/en-US/qlikview/April2020/Subsystems/Client/Content/QV_QlikView/LoadData/best-practices-data-modeling.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://help.qlik.com/en-US/qlikview/April2020/Subsystems/Client/Content/QV_QlikView/application-performance-optimization.htm" target="_blank" rel="noopener"&gt;https://help.qlik.com/en-US/qlikview/April2020/Subsystems/Client/Content/QV_QlikView/application-performance-optimization.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Hopefully that will get you the info you need.&lt;/P&gt;&lt;P&gt;Maybe this Design Blog too:&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.qlik.com/t5/Qlik-Design-Blog/Data-Modelling-Clarity-vs-Speed/ba-p/1473644" target="_blank"&gt;https://community.qlik.com/t5/Qlik-Design-Blog/Data-Modelling-Clarity-vs-Speed/ba-p/1473644&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;BR /&gt;Brett&lt;/P&gt;</description>
      <pubDate>Thu, 11 Jun 2020 17:50:09 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Multiple-Dimension-Tables-linked-to-Fact-table-using-same-key/m-p/1718029#M592331</guid>
      <dc:creator>Brett_Bleess</dc:creator>
      <dc:date>2020-06-11T17:50:09Z</dc:date>
    </item>
  </channel>
</rss>

