<?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: datawarehouse concepts in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/datawarehouse-concepts/m-p/763835#M271503</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="margin-bottom: 1em; font-size: 15px; color: #222222; font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif;"&gt;&lt;STRONG&gt;Database&lt;/STRONG&gt;&lt;/P&gt;&lt;OL style="margin-bottom: 1em; margin-left: 30px; font-size: 15px; color: #222222; font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif;"&gt;&lt;LI&gt;Used for Online Transactional Processing (OLTP) but can be used for other purposes such as Data Warehousing. This records the data from the user for history.&lt;/LI&gt;&lt;LI&gt;The tables and joins are complex since they are normalized (for RDMS). This is done to reduce redundant data and to save storage space.&lt;/LI&gt;&lt;LI&gt;Entity – Relational modeling techniques are used for RDMS database design.&lt;/LI&gt;&lt;LI&gt;Optimized for write operation.&lt;/LI&gt;&lt;LI&gt;Performance is low for analysis queries.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;SPAN style="margin-bottom: 1em; font-size: 15px; color: #222222; font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif;"&gt;&lt;STRONG&gt;Data Warehouse&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;OL style="margin-bottom: 1em; margin-left: 30px; font-size: 15px; color: #222222; font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif;"&gt;&lt;LI&gt;Used for Online Analytical Processing (OLAP). This reads the historical data for the Users for business decisions.&lt;/LI&gt;&lt;LI&gt;The Tables and joins are simple since they are de-normalized. This is done to reduce the response time for analytical queries.&lt;/LI&gt;&lt;LI&gt;Data – Modeling techniques are used for the Data Warehouse design.&lt;/LI&gt;&lt;LI&gt;Optimized for read operations.&lt;/LI&gt;&lt;LI&gt;High performance for analytical queries.&lt;/LI&gt;&lt;LI&gt;Is &lt;EM&gt;usually&lt;/EM&gt; a Database&lt;/LI&gt;&lt;/OL&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 21 Mar 2015 22:11:49 GMT</pubDate>
    <dc:creator>robert_mika</dc:creator>
    <dc:date>2015-03-21T22:11:49Z</dc:date>
    <item>
      <title>datawarehouse concepts</title>
      <link>https://community.qlik.com/t5/QlikView/datawarehouse-concepts/m-p/763833#M271501</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;what is differance between database and datawarehouse?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 21 Mar 2015 15:24:56 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/datawarehouse-concepts/m-p/763833#M271501</guid>
      <dc:creator />
      <dc:date>2015-03-21T15:24:56Z</dc:date>
    </item>
    <item>
      <title>Re: datawarehouse concepts</title>
      <link>https://community.qlik.com/t5/QlikView/datawarehouse-concepts/m-p/763834#M271502</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ask Google exactly the same question, there are some really nice pages. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Of course I'd like to answer your question, but it's gonna be a story and those stories are on the web already. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Grtz Fred&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 21 Mar 2015 21:26:45 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/datawarehouse-concepts/m-p/763834#M271502</guid>
      <dc:creator>fred_s</dc:creator>
      <dc:date>2015-03-21T21:26:45Z</dc:date>
    </item>
    <item>
      <title>Re: datawarehouse concepts</title>
      <link>https://community.qlik.com/t5/QlikView/datawarehouse-concepts/m-p/763835#M271503</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="margin-bottom: 1em; font-size: 15px; color: #222222; font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif;"&gt;&lt;STRONG&gt;Database&lt;/STRONG&gt;&lt;/P&gt;&lt;OL style="margin-bottom: 1em; margin-left: 30px; font-size: 15px; color: #222222; font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif;"&gt;&lt;LI&gt;Used for Online Transactional Processing (OLTP) but can be used for other purposes such as Data Warehousing. This records the data from the user for history.&lt;/LI&gt;&lt;LI&gt;The tables and joins are complex since they are normalized (for RDMS). This is done to reduce redundant data and to save storage space.&lt;/LI&gt;&lt;LI&gt;Entity – Relational modeling techniques are used for RDMS database design.&lt;/LI&gt;&lt;LI&gt;Optimized for write operation.&lt;/LI&gt;&lt;LI&gt;Performance is low for analysis queries.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;SPAN style="margin-bottom: 1em; font-size: 15px; color: #222222; font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif;"&gt;&lt;STRONG&gt;Data Warehouse&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;OL style="margin-bottom: 1em; margin-left: 30px; font-size: 15px; color: #222222; font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif;"&gt;&lt;LI&gt;Used for Online Analytical Processing (OLAP). This reads the historical data for the Users for business decisions.&lt;/LI&gt;&lt;LI&gt;The Tables and joins are simple since they are de-normalized. This is done to reduce the response time for analytical queries.&lt;/LI&gt;&lt;LI&gt;Data – Modeling techniques are used for the Data Warehouse design.&lt;/LI&gt;&lt;LI&gt;Optimized for read operations.&lt;/LI&gt;&lt;LI&gt;High performance for analytical queries.&lt;/LI&gt;&lt;LI&gt;Is &lt;EM&gt;usually&lt;/EM&gt; a Database&lt;/LI&gt;&lt;/OL&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 21 Mar 2015 22:11:49 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/datawarehouse-concepts/m-p/763835#M271503</guid>
      <dc:creator>robert_mika</dc:creator>
      <dc:date>2015-03-21T22:11:49Z</dc:date>
    </item>
  </channel>
</rss>

