Allocated memory exceeded after loading the qvw file

[#1]

Hello All,

We are using version 11.20 personal deskop edition. when loaded with qvw file we get an error indicating "Allocated memory exceeded" on the dashboards. Can`anyone give us documentation pointers to fix the error...

QVW File was created on Licensed version of QlikView and we are opening on a Personal Edition

Appreciate your help...

Thanks

Subbarao

[jpenuliar]

Have a look at discussion below:

Allocated memory exceeded in qvw file

[petter]

Personal Edition can't open QVW-files that have been made in a licensed version unless it is made by Qlik employees who has a special license that enables them to make such QVW-files...

[qlikviewwizard]

ksubbarao‌

You are opening the QVW in Personal Edition. Did you lease the license from server?

[ashfaq_haseeb]

Hi,

This could happen in case you are using heavy calculation in front end that requires more ram to process it.

You have 2 options

1) try by increasing ram

2) if you can try to take your front end calculation to backed and use simple expression in front end.

Hopefully it should resolve your issue.

Regards

ASHFAQ

[qlikviewwizard]

Hi ashfaq_haseeb

Good points. Thank you. You have been not in community since many days.

[jagan]

Hi,

Generally this types of issues are solved by increasing the RAM in your machine. If you have any high end machine then check in that machine.

This issues are performance issues.

Also with some careful precautions this can be avoided

- Don't display huge data in tables like Table box, Straight Table, Pivot Table,

- Don't display all charts in a single shot, show/hide by using buttons or split into sheets.

- Perform all possible calculations in the script level itself and bring some flags wherever required.

- Load only required data instead of loading all the data in the database and required columns so that the size of the QVW file will be reduced.

- Always make your key columns as numeric, so that the joins will be faster.  If your data is Text then use AutoNumber(),

- If you are not using Time part in the date fields for analysis remove it by using Date(Floor(DateFieldName)), a lot of memory will be saved.

- Restrict displaying huge data in tables by forcing users to select some filters.

- Try to create Star schema data model.

- Last but not the least remove all your synthetic keys and Circular references for better performance

Hope this helps you.

Regards,

Jagan.