Qlik Community

QlikView Scripting

Discussion Board for collaboration on QlikView Scripting.

Announcements
QlikView Fans! We’d love to hear from you.
Share your QlikView feedback with the product team… Click here to participate in our 5-minute survey.
Rules, plus terms and conditions, can be found here.
Not applicable

Windows/Web I/O about Section Limitation

Hi QlikView Sir/Madam,

I'd like to ask, for example, I have a test.qvw file, its size is 10M, then I have some section Access setup in hidden script. Limit User A can view only half of data (5M). Then I using User A to open this file. What's the Windows/Web I/O Size? 10M or 5M?

Thanks a lot in advanced,

Vicky

Tags (1)
1 Solution

Accepted Solutions

Re: Windows/Web I/O about Section Limitation

Hi Vicky,

In short, what reducing in section access does is opening the whole copy of the document into memory, checking for the values related from section access table, then removing non related rows from memory. So the final accesible copy in memory of the document will have only the rows related and therefore, use less memory.

It's like when you open the document locally as admin, select one of the users, go to the File menu, then Reduce Data, Keep Possible Values, then save. The resulting document will use less space in disk, since it has been actually reduced.

Hope that makes sense.

Miguel

3 Replies

Re: Windows/Web I/O about Section Limitation

Hi Vicky,

In short, what reducing in section access does is opening the whole copy of the document into memory, checking for the values related from section access table, then removing non related rows from memory. So the final accesible copy in memory of the document will have only the rows related and therefore, use less memory.

It's like when you open the document locally as admin, select one of the users, go to the File menu, then Reduce Data, Keep Possible Values, then save. The resulting document will use less space in disk, since it has been actually reduced.

Hope that makes sense.

Miguel

Not applicable

Re: Windows/Web I/O about Section Limitation

Thank you Miguel, I think I understand. Once open the .qvw file. The system fetch the whole copy to the memory.

Re: Windows/Web I/O about Section Limitation

Hi Vicky,

Yes, the system fetches the whole copy, but then reduces and leaves only the subset of data that corresponds to each user depending on the reduction by section access. In your example, will leave the 5M dataset (reduced) instead of the 10M dataset (whole file).

Hope that makes sense.

Miguel

Community Browser