<?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 Model review in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Data-Model-review/m-p/923989#M529984</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I would like some feedback on this data model I have created for my organization. The model contains about 110 million rows. The performance in Ajax is actually quite fast. I would just like to hear what people think about this type of design. I used the patients as the center of the snowflake and then branched off on hospital visits, ambulatory visits, and home health visits. I could not use a master calendar with this table, nor do I think I would want to, as I want to see all a patients visits say in the hospital, when I choose their ambulatory encounter.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I also had to reload many of the dimension tables, as the dimensions are attached to each fact table with a left keep. So if I use a resident pull from them, I only get those providers from that fact table. I just would like to hear what people think and I am open to suggestions on how to make this better!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 31 Jul 2015 13:09:18 GMT</pubDate>
    <dc:creator />
    <dc:date>2015-07-31T13:09:18Z</dc:date>
    <item>
      <title>Data Model review</title>
      <link>https://community.qlik.com/t5/QlikView/Data-Model-review/m-p/923989#M529984</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I would like some feedback on this data model I have created for my organization. The model contains about 110 million rows. The performance in Ajax is actually quite fast. I would just like to hear what people think about this type of design. I used the patients as the center of the snowflake and then branched off on hospital visits, ambulatory visits, and home health visits. I could not use a master calendar with this table, nor do I think I would want to, as I want to see all a patients visits say in the hospital, when I choose their ambulatory encounter.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I also had to reload many of the dimension tables, as the dimensions are attached to each fact table with a left keep. So if I use a resident pull from them, I only get those providers from that fact table. I just would like to hear what people think and I am open to suggestions on how to make this better!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 31 Jul 2015 13:09:18 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Data-Model-review/m-p/923989#M529984</guid>
      <dc:creator />
      <dc:date>2015-07-31T13:09:18Z</dc:date>
    </item>
  </channel>
</rss>

