4 Replies Latest reply: Nov 15, 2011 6:50 AM by Deepak Vadithala RSS

    details of qlikview



      iam new to clik view business intelligence? basically i work on hyperion reportiing?recently one of our projects was going to start on qlikview?

      i want to know the details of qlikview compared to hyperion essbase (or) planning?

      how it works?


      Thanks in Advance


        • details of qlikview

          Hi Madhukar,

          I don't have experience in Hypherion, so I can't tell you the comparision. Based on my experience what I can say that first you need to understand the system first then start desiging the data model(Star schema & Snowflake recommended) then load the data into qlikview. Once the data is loaded in to qlikview you can do offline analysis as well.

          Once the data has been loaded you can start developing the reports and dashboards as per the user requirement.






          • details of qlikview
            renjith pl

            You can actually go through the Qlikview Reference Manual. It will explain you every thing about qlikview. Most of the qlikview users get knowledge from Reference manual, its really useful.

            I am unaware of Hyperion, But through Qlikview you can do anykind of reporting in a easy, faster way. Qlikview rocks. :)



            • details of qlikview

              you can learn qlikview speedly by comparing architecture of qlikview with architecture of hyperion.


              • Re: details of qlikview
                Deepak Vadithala



                I understand this is very old post. However, I thought I would share my understanding if you are still interested to know.


                The data records are read into the memory, so that all the processing of data may be done through memory. I am sure you know this bit. QlikView treats all the data as Data Element Type (Columns / Fields) and Data Element Values (Values / Records). So each different data element value of each data element type is assigned a binary code and the data records are stored in binary-coded form and they are also sorted. By using the binary coding, very quick searches can be done on the tables. Also, QlikView removes the redundant information information and reduces the amount of data. However, the redundant information in stored as seperately with the frequencies for each unique data element value and across each data element type. When user makes a selection on data element values then the implied selection (possible values) are kept track seperately to present them to the user. By this process QlikView can perform rapid linear searches.


                I understand this is not in detail but just a quick overview. I hope this helps!


                Good luck!


                Cheers - DV