Book Image

QlikView for Developers Cookbook

By : Stephen Redmond
Book Image

QlikView for Developers Cookbook

By: Stephen Redmond

Overview of this book

QlikView has been around since 1993, but has only really taken off in recent years as a leader in the in-memory BI space and, more recently, in the data discovery area. QlikView features the ability to consolidate relevant data from multiple sources into a single application, as well as an associative data model to allow you to explore the data to a way your brain works, state-of-the-art visualizations, dashboard, analysis and reports, and mobile data access. QlikView for Developers Cookbook builds on your initial training and experiences with QlikView to help you become a better developer. This book features plenty of hands-on examples of many challenging functions. Assuming a basic understanding of QlikView development, this book provides a range of step-by-step exercises to teach you different subjects to help build your QlikView developer expertise. From advanced charting and layout to set analysis; from advanced aggregations through to scripting, performance, and security, this book will cover all the areas that you need to know about. The recipes in this book will give you a lot of the information that you need to become an excellent QlikView developer.
Table of Contents (19 chapters)
QlikView for Developers Cookbook
Credits
Foreword
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Reducing the number of distinct values


QlikView's columnar data storage method is extremely efficient at storing data because it does not store repeating values. Each unique value is only stored once. This means that, in general, a QlikView in-memory data set will always be much smaller than the original data source.

This efficiency is lost, however, when the data is highly distinct. The more distinct the values that exist within the data, the more space that QlikView will need to store it in memory. The worst offenders for this are often ID fields and time stamps, and if we can remove these, then we will make our document more efficient.

Getting ready

Load the following script:

// Build a list of city/countries
City_Country:
Load * Inline [
  CityID, City, Country
  1, Boston, USA
  2, New York, USA
  3, Los Angeles, USA
  4, Mexico City, Mexico
  5, Vancouver, Canada
  6, Montreal, Canada
  7, London, UK
  8, Manchester, UK
  9, Berlin, Germany
  10, Paris, France
];

Store City_Country into...