What will changing the "Max Values in Current Selections" via the registry key MaxCurSelEntries to affect all reports do?
I was asked by a developer to add this on our Test server and I want to be sure this won't negatively affect performance. Being more on the admin side of QlikView I don't know if allowing a user to select 100 values in a filter will cause the app bring back a large enough dataset that would increase disk IO or consume a massive amount of memory and cause problems.
Also, Why does this setting at the Application level not stick with the app when it is published. I can only assume it is to protect server performance.
Re: What will changing the "Max Values in Current Selections" via the registry key MaxCurSelEntries to affect all reports do?
The amount of possibly available values for selections itself isn't really important especially not by hundreds of values. More important is the size from whole dataset and how the datamodel is designed. By a poor designed datamodel is already one wrong single selections enough to explode the cpu+ram.