Skip to main content
Qlik Introduces a New Era of Visualization! READ ALL ABOUT IT
Showing results for 
Search instead for 
Did you mean: 
Partner - Creator III
Partner - Creator III

key size in qlik sense

All my table primary key are 16- 20 digits(numeric). When i loaded the join was not happening proper. So i converted i to text  while retrieving from database. But I am seeing a performance degrade in the SQL query with cast. Is there any better solution for this issue, other than converting to text at DB level

2 Replies

try using Autonumber functions


The max. number of digits to keep a value numeric is 14-15 (by a join 15 should work and by other processings like a mapping only 14). This is caused by the in Qlik used number-system. This meant you need to load the keys as strings (this could be done in Qlik with text() which meant it's not necessary to do it in the database) as far you want to store the data into qvd's or applying a joining or similar actions but by associate the tables within the datamodel you could use an autonumber() on these key-fields.

Before doing it I would check if the keys couldn't be reduced in regard to the number of digits - maybe they are also with lesser digits unique.

- Marcus