Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
QlikView for Developers

You're reading from   QlikView for Developers Design and build scalable and maintainable BI solutions

Arrow left icon
Product type Paperback
Published in Jun 2017
Publisher Packt
ISBN-13 9781786469847
Length 546 pages
Edition 1st Edition
Arrow right icon
Authors (2):
Arrow left icon
Miguel  Angel Garcia Miguel Angel Garcia
Author Profile Icon Miguel Angel Garcia
Miguel Angel Garcia
Barry Harmsen Barry Harmsen
Author Profile Icon Barry Harmsen
Barry Harmsen
Arrow right icon
View More author details
Toc

Table of Contents (17) Chapters Close

Preface 1. Meet QlikView FREE CHAPTER 2. What's New in QlikView 12? 3. Seeing is Believing 4. Data Sources 5. Data Modeling 6. Styling Up 7. Building Dashboards 8. Scripting 9. Data Modeling Best Practices 10. Basic Data Transformation 11. Advanced Expressions 12. Set Analysis and Point In Time Reporting 13. Advanced Data Transformation 14. More on Visual Design and User Experience 15. Security Index

Chapter 4. Data Sources

We've completed the "seeing is believing" phase with big success. We've shown HighCloud Airlines the potential value that QlikView can bring to their business and how they will be able to give their raw data the meaning that their business requires to make everyday decisions. Now, the natural question that arises after seeing what QlikView can do on the frontend is: what type of database does QlikView require to work?

The straight answer to this question is simply that QlikView does not necessarily require a specific database or Data Warehouse (DWH) to pull data from. It can benefit from using a DWH, but that is not required. However, the data must reside somewhere in order to be able to pull it into QlikView, visualize it, discover patterns in it, and build all kinds of charts with it. That "somewhere" can be almost any standard database, flat file (for example, .xlsx or .csv), web page, web service, and so on, or even any...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime