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

Simplify, simplify, simplify – never have subtables that you don't need

Does good database design give the best results in QlikView?


QlikView's data model design philosophy doesn't follow that of good database design; in fact, to get the best out of QlikView it is nearly the exact opposite.

For anyone who has been involved with database design, for many years the philosophy has been to have a fully normalized data structure. For those who don't know what this means, in simplistic terms, don't store anything twice. So, if you have, for example, a Manufacturer Name in each Product record, you should create a separate table to hold all the Manufacturer Names and a Key and then just store the appropriate Key in each of the Product records.

The Manufacturer Name will only be stored once in the database, taking up less space.

How to do it

QlikView quite happily works with a fully normalized database. However, from a QlikView perspective, the most efficient data model is one flat file with...