Book Image

Mastering QlikView

By : Stephen Redmond
Book Image

Mastering QlikView

By: Stephen Redmond

Overview of this book

Table of Contents (14 chapters)
Mastering QlikView
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Preface

This is a book about mastery. But what does this mean? What does being a QlikView master mean?

When I wrote QlikView for Developers Cookbook, Packt Publishing, I started the preface with the sentence:

"There is no substitute for experience."

When it comes to QlikView, experience is the thing that makes a difference. Experience is the difference between the developers who can create good applications and the consultants who can create real business solutions that solve real business problems.

I have been working with QlikView since 2006, and in this time, I have created some fantastic solutions. I also created applications that I cringe to look at today. I like to think that I have mastered the subject, even though I am still learning.

At CapricornVentis, I work with one of the brightest bunch of consultants; it has ever been my pleasure to work with them. I get to teach a lot but I also get to learn a tremendous amount from these guys. We are constantly pushing the boundaries of the product to get to the right solution. As a beginner in this area, I would have wanted to work for an organization like CapricornVentis, where I could really learn and grow as a consultant.

Let's be clear; I do not know every little detail about QlikView, but I do know most of them. What I think I know, and know really well, are the important things to know about when creating QlikView solutions. This knowledge is what I have tried to distil down into this book.

You won't be a master by just reading this book. As Alfred Korzybski famously stated:

"The map is not the territory."

This book is not an ultimate mastering guide, rather is a like a map that guides us towards our common destination—to become a QlikView master. Study the map well and you will get there.

Qlik Sense

During the development of this book, Qlik released their next generation product, Qlik Sense. Qlik Sense is not, currently, a replacement product for QlikView, and Qlik has announced that they will have a two-product strategy and sell QlikView for guided BI applications and Qlik Sense for self-service BI applications. A new version, QlikView 12.0, is slated for release in the second half of 2015.

While Qlik Sense is a new product, it is built on the same heritage as QlikView. There is a new data engine, QIX, that stores the data in a format more columnar than that of QlikView. However, the inference engine is still the same (green, white, and gray). The script syntax is still the same; in fact, we can use QlikView scripts in Qlik Sense. The frontend is very different because it is based on a new web design, but the expression syntax is still the same.

Therefore, much of what is written in this book about QlikView will still apply to Qlik Sense. Anyone who masters QlikView will be well on their way to mastering Qlik Sense.

What this book covers

Chapter 1, Performance Tuning and Scalability, is where we look at understanding how QlikView stores its data so that we can optimize that storage in our applications. We will also look at topics such as Direct Discovery and testing implementations using JMeter.

Chapter 2, QlikView Data Modeling, looks in detail at dimensional data modeling and learning about fact and dimension tables and using best practices from Ralph Kimball in QlikView. We also learn about how to handle slowly changing dimensions (SCDs), multiple fact tables, and drilling across with document chaining.

Chapter 3, Best Practices for Loading Data, is where we look at implementing ETL strategies with QVD files. We also introduce QlikView Expressor.

Chapter 4, Data Governance, looks at areas such as implementing metadata in QlikView and managing our implementation with QlikView Governance Dashboard.

Chapter 5, Advanced Expressions, is where we look at areas such as the Dollar-sign Expansion, set analysis, and vertical calculations using Total and Aggr.

Chapter 6, Advanced Scripting, looks at optimizing loads, Dollar-sign Expansion in the script, and control structures. We also introduce the concept of code reuse.

Chapter 7, Visualizing Data, is where we look at the historical background to data visualization; we gain an understanding of the human relationship with numbers and learn some good design principles to bring to our applications.

What you need for this book

You need a copy of QlikView Desktop, which you can download for free from http://www.qlikview.com/download. After this, you shouldn't need anything else. You can also test the examples in Qlik Sense.

To demonstrate the different techniques and functions, I will usually get you to load a table of data. We do this using the INLINE function. For example:

Load * Inline [
  Field1, Field2
  Value1, Value2
  Value3, Value4
];

This will load a table with two fields, Field1 and Field2, and two rows of data.

Most of the time, this type of table is enough for what we need to do. In a few examples, where I need you to use more data than that, we will use publicly available data sources.

Who this book is for

This is not a beginner's book. This book is for anyone who has learned QlikView or Qlik Sense—either from formal training, online resources, or QlikView 11 for Developers, Miguel García and Barry Harmsen, Packt Publishing—and now wants to take their learning to a higher level.

Conventions

In this book, you will find a number of text styles that distinguish between different kinds of information. Here are some examples of these styles and an explanation of their meaning.

Code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles are shown as follows: "In the QVScriptGenTool_0_7 64Bit\Analyzer folder there is a ZIP file called FolderTemplate.zip."

A block of code is set as follows:

Sales:
Load * INLINE [
  Country, Sales
  USA, 1000
  UK, 940
  Japan, 543
];

When we wish to draw your attention to a particular part of a code block, the relevant lines or items are set in bold:

Sales:
Load * INLINE [
  Country, Sales
  USA, 1000
  UK, 940
  Japan, 543
];

Any command-line input or output is written as follows:

C:\Program Files\QlikView\qv.exe

New terms and important words are shown in bold. Words that you see on the screen, for example, in menus or dialog boxes, appear in the text like this: "Click on the Execution tab."

Note

Warnings or important notes appear in a box like this.

Tip

Tips and tricks appear like this.

Reader feedback

Feedback from our readers is always welcome. Let us know what you think about this book—what you liked or disliked. Reader feedback is important for us as it helps us develop titles that you will really get the most out of.

To send us general feedback, simply e-mail , and mention the book's title in the subject of your message.

If there is a topic that you have expertise in and you are interested in either writing or contributing to a book, see our author guide at www.packtpub.com/authors.

Customer support

Now that you are the proud owner of a Packt book, we have a number of things to help you to get the most from your purchase.

Downloading the example code

You can download the example code files from your account at http://www.packtpub.com for all the Packt Publishing books you have purchased. If you purchased this book elsewhere, you can visit http://www.packtpub.com/support and register to have the files e-mailed directly to you.

Errata

Although we have taken every care to ensure the accuracy of our content, mistakes do happen. If you find a mistake in one of our books—maybe a mistake in the text or the code—we would be grateful if you could report this to us. By doing so, you can save other readers from frustration and help us improve subsequent versions of this book. If you find any errata, please report them by visiting http://www.packtpub.com/submit-errata, selecting your book, clicking on the Errata Submission Form link, and entering the details of your errata. Once your errata are verified, your submission will be accepted and the errata will be uploaded to our website or added to any list of existing errata under the Errata section of that title.

To view the previously submitted errata, go to https://www.packtpub.com/books/content/support and enter the name of the book in the search field. The required information will appear under the Errata section.

Piracy

Piracy of copyrighted material on the Internet is an ongoing problem across all media. At Packt, we take the protection of our copyright and licenses very seriously. If you come across any illegal copies of our works in any form on the Internet, please provide us with the location address or website name immediately so that we can pursue a remedy.

Please contact us at with a link to the suspected pirated material.

We appreciate your help in protecting our authors and our ability to bring you valuable content.

Questions

If you have a problem with any aspect of this book, you can contact us at , and we will do our best to address the problem.