Book Image

Learning Qlik Sense??: The Official Guide Second Edition - Second Edition

By : Christopher Ilacqua, QlikTech International AB, Henric Cronström, James Richardson
Book Image

Learning Qlik Sense??: The Official Guide Second Edition - Second Edition

By: Christopher Ilacqua, QlikTech International AB, Henric Cronström, James Richardson

Overview of this book

The intuitive and powerful Qlik Sense visual analytics software allows anyone to engage in data discovery, to explore your data, and find meaningful insights to empower your business. Qlik Sense lets you easily create personalized reports and visualizations and reveal essential connections to show new opportunities from every angle. Written by members of the Qlik Sense team, this book is the official guide from Qlik to understanding and using their powerful new product with fully updated coverage to the latest features of the most modern edition of Qlik Sense. Benefit from the vision behind the development of Qlik Sense and get to grips with how Qlik Sense can empower you as a data discovery consumer. Learn how to create your own applications for Qlik Sense to customize it to meet your personal needs for business intelligence, and how to oversee and administer the Qlik Sense data architecture. Finally, explore utilizing Qlik Sense to uncover essential data, with practical examples on finding and visualizing intelligence for sales figures, human resources information, travel expense tracking, and demographic data discovery.
Table of Contents (21 chapters)
Learning Qlik Sense® The Official Guide Second Edition
Credits
About the Authors
Acknowledgments
About the Reviewer
www.packtpub.com
Preface
Index

Structuring your data


In a database, there are rules about where different entities are stored. For instance, everything about the customers should be stored in the Customers table. A customer identifier is stored in this table, which means that the necessary data can be retrieved by a simple lookup in the Customers table. So, if you need to refer to a customer from another table, you just store this identifier in the other table.

Normalization

The identifier needs to be unique in the Customers table, so that every record can be addressed. Here the field is called a primary key. In other tables, duplicates may exist. For example, several records in the Orders table might refer to the same customer. If this is the case, the key is called a foreign key.

A consequence of this setup is that a database can have many tables, often thousands. One table for customers, one for orders, one for order lines, one for products, one for product groups, one for shippers, one for invoices, and so on. Each table...