Skip to main content
Announcements
Qlik Connect 2024! Seize endless possibilities! LEARN MORE
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

AutoNumber Alternatives?

Hello All,

We have a large data set, approximately 2 billion records in a facts table that will continue to grow overtime. The Facts table will be updated weekly by adding last week's records and removing the oldest week in the process. Most entries in the community related to performance indicate using Qlik generated IDs is the best way to go, reduces storage needs and improves performance.  However, a common problem listed when using AutoNumber() to generate these IDs is that the AutoNumber() function restarts the sequencing whenever a reload is performed. Does anyone happen to know if AutoNumberHash128() or AutoNumberHash256() ensure uniqueness across multiple reloads. We would prefer not to have to generate new IDs using AutoNumber() for the entire dataset each time we perform a reload.

I thank you in advance for you time and insight.

Best,
Carlos

2 Replies
maxgro
MVP
MVP

don't think hash (for hash collision), look at Gysbert answer here

Re: Hash Function

maybe an idea could be to store the last id and

rowno() + last id

rwunderlich
Partner Ambassador/MVP
Partner Ambassador/MVP

You can create persistent keys with the Hash* functions. Leave off the Autonumber() part.