Skip to main content

Best Practice for Synthetic keys/Synthetic Tables

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
Yoichi_Hirotake
Former Employee
Former Employee

Best Practice for Synthetic keys/Synthetic Tables

Last Update:

Nov 11, 2020 4:10:08 AM

Updated By:

Sonja_Bauernfeind

Created date:

Aug 12, 2014 1:11:07 AM

Regarding Synthetic keys/Synthetic Tables, the first recommendation is to read through this post created by Henric Cronström.

QlikView or Qlik Sense may end up using an excessive amount of time and/or memory when the number of composite keys/Synthetic Tables increases and depending on data amounts, table structure and other factors.

Unfortunately, the actual limitations are virtually impossible to predict, which leaves only trial and error as a practical method to determine them.

 

Best Practices: 

 

If they are UNINTENDED Synthetic keys/Synthetic Tables:

Please eliminate the Synthetic keys/Synthetic Tables as much as possible

If they are INTENDED Synthetic keys/Synthetic Tables:

Please do the performance test and find out the best data model based on the testing result.

Labels (1)
Contributors
Version history
Last update:
‎2020-11-11 04:10 AM
Updated by: