Book Image

QlikView Unlocked

By : Andrew Dove, Roger Stone
Book Image

QlikView Unlocked

By: Andrew Dove, Roger Stone

Overview of this book

QlikView Unlocked will provide you with new insights to get the very best from QlikView. This book will help you to develop skills to work with data efficiently. We will cover all the secrets of unleashing the full power of QlikView, which will enable you to make better use of the tool and create better results for future projects. In the course of this book, we will walk you through techniques and best practices that will enable you to be more productive. You will gain quick insights into the tool with the help of short steps called ”keys,” which will help you discover new features of QlikView. Moving on you will learn new techniques for data visualization, scripting, data modeling, and more. This book will then cover best practices to help you establish an efficient system with improved performance. We will also teach you some tricks that will help you speed up development processes, monitor data with dashboards, and so on. By the end of this book, you will have gained beneficial tips, tricks, and techniques to enhance the overall experience of working with QlikView.
Table of Contents (16 chapters)
QlikView Unlocked
About the Authors
About the Reviewers
Hidden Image List


Although the most efficient data model is a single flat file, this is rarely possible, and we need to have linked tables. This means that we will have at least one linking field. In most cases, this field is not presented to the user as it is likely to be code or a combination of fields.

In this case, we can take advantage of the Autonumber() function. Rather than storing the contents of the field in memory, it stores the internal pointer to this particular occurrence of the field content. We have also noticed that sometimes the pointer is only stored in the record header and not as a separate field, therefore saving a lot of space; however, this is not always the case.

This is especially useful if you have to create a key field (by combining individual fields) to avoid synthetic keys, as these can be extremely large and, by their use, completely unique.

Unfortunately there is a downside; in this case, it comes with a performance hit. We are back to our old friend, the Time/Space...