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

Synthetic keys and why they're sometimes bad news

Whenever you create two or more tables that have two or more fields with the same name, QlikView creates a synthetic key table to join them.


Old school logic has stated for a long time that Synthetic keys in the data model design are bad. This is not always the case, however, and in some cases, it is unavoidable.

How to do it

The best way to avoid Synthetic keys is to create a single field with all the fields concatenated together. This needs to be done in all linking tables. The result would be a cleaner and potentially more efficient design.

The problem with this approach is the amount of memory it can consume. The uniqueness of this new combined field means that the amount of memory used to store it is increased and not just in one table but all of them, as in the following simple example.

Current fields:


Number of unique entries

Bytes used

Invoice Date


500 (10 characters x 50)

Customer ID


800 (8 characters x...