ran out of memory - 2 querstions

[#1]

Hi,

I have previously asked about the issue where an error comes up to say "ran out of memory 2MB" - Inconsistency type D

Users have kindly pointed this is due to:

"This is an object-related error, not script-related. First identify the object. It should be obvious which one is causing all this hassle. Then try to open the document in QV Desktop and immediately switch to another sheet than the one where the object resides. Open Settings->Document Properties->Sheets , select the sheet with the annoying object , select the object and click Properties (to edit the object) or Delete to... just delete"

However, on latest app where this has happened this doesn't seem so obvious. The script is lengthy but works well and there are no synthetic keys. It's a table box that is causing the issue - essentially it seems to have too much data in it. Regardless of the fields contents used there seem to just become a point where it can't load any more data and so we get the error message noted above a cross over the data in the table box.

So,

1) is it the case and/or anyone experienced it where there seems to be a limit on data? The table has about 70 columns with up to 30,000 records in each time. However, thought the whole point of QV was it can mange so much data...? We could split data into several table boxes but this isn't ideal.

2) can the amount of memory be increased (assume this is an IT thing to be done outside QV desktop)

Appreciate any response.

Chris

[tresesco]

1) No such limit on data

2) Increasing RAM should help

[jagan]

Hi,

1. There is no limit on the data size, you should have better configuration(RAM, Cores etc) if you have more data.  Qlikview is in memory, so it stores all the data in RAM, there should be adequate RAM in your machine.

2. Increasing RAM will definitely help.

This error occurs because of performance issues,

1. If you are displaying huge data in Table objects you will get this, to overcome this you need to make user to select some filters by using the Calculation Condition option of the chart in General Tab.

For example: =GetSelectedCount(Year) > 0   -- This will force user to select year compulsorily, then only chart loads

2. Expressions - If you are using complex calculations or Calculated dimensions this error will occur.  Calculate as much as possible in script itself or by creating flags.

Hope this helps you.

Regards,

Jagan.

[Anonymous]

How much memory do you have in your computer?   We are using 64 bit version of QV and have 32 GB of memory in each of our developer computers.   One or our applications is 14 GB in size.   If we do not do as Jagan says and recommend the user limit the data by choosing a dimension, we do get out of memory errors on objects.  If this is an on-going issue, you can force the user to make selections on a chart for it to render.

I have several charts that we use this formula in the calculated condition field and if the user does not the chart gives this error.  Just substitute your dimension for the one in brown below