Hi, I have a table load with numerous calculated fields built by sum(if()) statements and grouped by the other fields. There are subsequent resident loads in which formulas work with the calculated fields to populate empty values in some fields based on the presence of related data in other fields. My laptop has 8GB of RAM and it loads fine there, but the server has 4GB RAM and is being crashed by the script. I believe I could break it into two scripts, have one go as far as building and transforming the key table, then saving it as a QVD, then have the remaining script run separately to populated and stratify that table.
I dabbled with store as qvd before, but it wasn't working so I wandered off. Can anyone give a general overview of the best practices layout and syntax (or a good current hyperlink) for breaking up a large server-crashing script into two or three more managable scripts using store as qvd? Would I be making separate QVWs, or doing something internal to the one script that allows QlikView and the server to catch a breath while loading the one script?
Here is an outline of the script I have:
Loads client data
Loads data about internal structure of client
Loads users and office data
Loads users and biometrics data - this is the one with a few dozen sum(if()) and the group by statement. My script pauses here for almost a minute to transform the table, then zooms on through what's left. I'd like to make a qvd off of this and have the remaining script look at that like a regular qvd file.
Five different biometric tables running formulas on Biometrics fields to populate empty values where possible (if needed data is present in other fields)
These go by pretty fast
A couple more tables extracting gender values from biometrics testnames specific to gender that have values in them
A table to stratify biometric values as normal or high with a bunch of dual if statements
Same as RiskBanding except it gives number messages instead of text messages (1=normal, 2 =at risk)