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.