Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
ALERT: The support homepage carousel is not displaying. We are working toward a resolution.

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:

Dec 22, 2025 6:09:27 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.

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:
2 weeks ago
Updated by: