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

Qlikview security causing long reload time

Hi everyone,

I have a Qlikview app with a security load in as well.

If I put the security load at the end of the script, the app builds in half an hour.

If I put the security at the very beginning of the app, the app loads in 3 hours.

what could be causing this? The security load takes like 1 second.

thanks,

Stefan

11 Replies
varshavig12
Specialist
Specialist

Security load... Do you mean section access ?

Anonymous
Not applicable
Author

that is correct

DavidFoster1
Specialist
Specialist

Section Access has to be the first code (only Binary load can be before) in the app before any data is loaded.

Putting it at the end means that it is ignored.

It is interesting that it had such a big impact on load times. Are there a lot of security filters?

varshavig12
Specialist
Specialist

I'm not very sure,

But, what you can try is,

Create a new qvw of section access and then binary load it in your main qvw.

Note: I have never done this, but you can try

stigchel
Partner - Master
Partner - Master

Like said above, the section access part has to be loaded first. The fact that this adds so much load time suggests to me that there are probably some synthetic keys being created between the access table and the application. These won't show in your table view as they are hidden. If you are linking on multiple fields, consider using composite keys. You can test your data model between access and application by commenting your section access statements to load the access table as a 'normal' table so you can look at the data model.

MK9885
Master II
Master II

The best way to avoid load time is to create another qvw as source file and do the binary load for your Data Model. And add your Section Access script after the binary load in source file.

Thanks.

cwolf
Creator III
Creator III

Sorry, but it does not matter where the Section Access is loaded. You can do it at first, at last or in the middle of a script. It's only important that it starts with a "SECTION Access;" and ends with a "SECTION Application;". Normally, there are no problems.

Maybe you have forgott the line "SECTION Application;" after your section access load?

MK9885
Master II
Master II

I agree, it actually doesn't matter where SA script is placed.

jonathandienst
Partner - Champion III
Partner - Champion III

I agree with Christian. There is no requirement to perform section access first. Its usually one of the last steps in the load script in most of my applications. Indeed, if you want to use generic keys in your section access, you can only build these keys after loading the model.

The only reason for loading SA first would be if you want to place it in the hidden script tab.

Logic will get you from a to b. Imagination will take you everywhere. - A Einstein