topic Re: Memory issue when section access is applied in QlikView

Memory issue when section access is applied

Thu, 21 Sep 2017 04:27:51 GMT

Hi experts,

When I apply a section access on a dashboard and then reopen it with desktop client, the memory usage grows horribly that I cannot even open the dashboard.

What happens?

Re: Memory issue when section access is applied

tresB — Thu, 21 Sep 2017 04:48:27 GMT

Perhaps, the section access is not being properly managed, I would guess somehow it is causing to create synthetic keys. Could you share your script snippet?

Re: Memory issue when section access is applied

Thu, 21 Sep 2017 07:01:02 GMT

However I can open the file when section access is not applied.

Everything including data model is the same.

Therefore I do not think it is caused by synthetic keys.

Re: Memory issue when section access is applied

tresB — Thu, 21 Sep 2017 07:08:47 GMT

If SA is properly applied, there would not be any synthetic keys. However, if there is any mistake and SA table is treated like in a section application, it could.

Re: Memory issue when section access is applied

marcus_sommer — Thu, 21 Sep 2017 08:28:29 GMT

Just comment the section access; statement out but load this table and than take a look within the tableviewer if there are any synthetic keys or circular references and also how many records are included (maybe with the debugger to limit the number of records).

- Marcus

Re: Memory issue when section access is applied

Thu, 21 Sep 2017 08:50:02 GMT

I comment the section access; statement, disable the section access, reload the dashboard and then open the table viewer.

The dashboard do not have synthetic keys and circular references.

The largest table (which is the fact table in star schema) has 18 millions records.

Re: Memory issue when section access is applied

Thu, 21 Sep 2017 08:50:38 GMT

I comment the section access; statement, disable the section access, reload the dashboard and then open the table viewer.

The dashboard do not have synthetic keys and circular references.

Re: Memory issue when section access is applied

marcus_sommer — Thu, 21 Sep 2017 08:58:37 GMT

It sounds quite strange - even with some issues within the datamodel should a star-scheme model with 18 M records not consume so much RAM. Please provide a screenshot of the table-viewer and which of the tables is the section access table.

- Marcus

Re: Memory issue when section access is applied

Fri, 22 Sep 2017 08:24:10 GMT

I create a new dashboard and copy everything to the new dashboard.

Nothing changes, but it works now.