I think the problem is that there are fields in my application extract that are the same as in the other extracts I use. And because I am new to QV I do not really know when to use Load, Concatenate Load, Join, etc...
At the moment I have:
- Load Account Extract
- Load Transaction Extract
- Concatenate Load Transaction Extract (x 20)
- Load Application Extract.
I then get the following message at the end:
One or more loops have been detected in your database structure. Loops may cause ambiguous results and should therefore be avoided. QlikView will cut the loop(s) by setting one or more tables as loosely coupled. Settings for loosely coupled tables can be modified after script execution in the tables page of the document properties dialog.
And then all my Transaction data is wrong and I get the memory error message. If I choose concatenate load some of my other chart data is wrong!
There are fields in the Application extract that are the same as in the Account Extract, which load statment should I use?
Below points will be of some help to you:
It's hard to say what the issue is right away like this. The actual file size usually has little to do with the amount of RAM consumed when calculating objects. This error message can occur for several reasons. If it's a chart it is because of your expressions. You either have too much data, to long, or a really bad if/else statement in one of your expressions.
However, here are a few things that are usually present in objects where Out of object memory occurs.
As a first step, you look at the number of fields being included in the application and validate that they are all required. Fields loaded but not referenced in any sheet objects will still use memory.
Pivot tables give the user a massive amount of flexibility but basic straight tables are less memory intensive in large data volume implementations.
Removing data that is not required from your data model can reduce the volume and uniqueness of the data model. You can simply comment the columns out to ensure that if they are needed at a later date you can easily add them again.
Do not write complexformulas in your chart expressions. Try to do all the calculations in the script part.
Also, try to avoid synthetic keys in your data model. They are not always very harmful but can cause serious problems if your database is not proper.