<?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: Database Layout in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Database-Layout/m-p/108970#M750945</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi &lt;/P&gt;&lt;P&gt;in order to work more efficiently and allow users more interaction with the data &lt;/P&gt;&lt;P&gt;the second one is better for any type of analytics , &lt;/P&gt;&lt;P&gt;this way you'll allow users to be able to select specific months or ranges ,&lt;/P&gt;&lt;P&gt;it'll be much easier&amp;nbsp; to create chart to display the data &lt;/P&gt;&lt;P&gt;and because it so easy to get from the first to the second one using cross table function in the script &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;it's a no brainier &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 05 Nov 2018 20:04:32 GMT</pubDate>
    <dc:creator>lironbaram</dc:creator>
    <dc:date>2018-11-05T20:04:32Z</dc:date>
    <item>
      <title>Database Layout</title>
      <link>https://community.qlik.com/t5/QlikView/Database-Layout/m-p/108969#M750944</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have been told that QV works better if the raw data is setup in vertical form not horizontal form:&lt;/P&gt;&lt;P&gt;This is how my data looks now in Excel...&lt;BR /&gt;We have a monthly forecast (Column E) and the results of future forecasts are to the right. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG alt="Capture.JPG" class="jive-image image-1" src="https://community.qlik.com/legacyfs/online/217570_Capture.JPG" style="height: 55px; width: 620px;" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG alt="Captu1re.JPG" class="jive-image image-2" src="https://community.qlik.com/legacyfs/online/217571_Captu1re.JPG" style="height: auto;" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Which is the preferred ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Nov 2020 16:16:04 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Database-Layout/m-p/108969#M750944</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2020-11-25T16:16:04Z</dc:date>
    </item>
    <item>
      <title>Re: Database Layout</title>
      <link>https://community.qlik.com/t5/QlikView/Database-Layout/m-p/108970#M750945</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi &lt;/P&gt;&lt;P&gt;in order to work more efficiently and allow users more interaction with the data &lt;/P&gt;&lt;P&gt;the second one is better for any type of analytics , &lt;/P&gt;&lt;P&gt;this way you'll allow users to be able to select specific months or ranges ,&lt;/P&gt;&lt;P&gt;it'll be much easier&amp;nbsp; to create chart to display the data &lt;/P&gt;&lt;P&gt;and because it so easy to get from the first to the second one using cross table function in the script &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;it's a no brainier &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 Nov 2018 20:04:32 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Database-Layout/m-p/108970#M750945</guid>
      <dc:creator>lironbaram</dc:creator>
      <dc:date>2018-11-05T20:04:32Z</dc:date>
    </item>
    <item>
      <title>Re: Database Layout</title>
      <link>https://community.qlik.com/t5/QlikView/Database-Layout/m-p/108971#M750946</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Just the problem is the sheer volume of data. plus having to convert it from horizontal to vertical.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have 500 skus, 36 months of data.. so right off the bat - 18,000 rows of data.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 Nov 2018 20:08:16 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Database-Layout/m-p/108971#M750946</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2018-11-05T20:08:16Z</dc:date>
    </item>
    <item>
      <title>Re: Database Layout</title>
      <link>https://community.qlik.com/t5/QlikView/Database-Layout/m-p/108972#M750947</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Concur with Liron.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;18000 rows of data isnt a problem at all for Qlik. Have worked with apps with 100s of millions of rows.&lt;/P&gt;&lt;P&gt;As data size increases efficient modeling of the data becomes more important.&lt;/P&gt;&lt;P&gt;But IMHO 18k is nothing for qlik &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can easily do the conversion using cross table load.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.qlik.com/qlik-blogpost/3628"&gt;The Crosstable Load&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 Nov 2018 21:44:34 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Database-Layout/m-p/108972#M750947</guid>
      <dc:creator>dplr-rn</dc:creator>
      <dc:date>2018-11-05T21:44:34Z</dc:date>
    </item>
  </channel>
</rss>

