Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Crosstable (memory use)

Hello All,

I need to consolidate fields and see that using a crosstable is the best way to do that. Below is my script. I don't think I am making this load as efficient as possible and my guess is bc I am using a resident load with each crosstable? (although that is what I need sourced). If you look at the first crosstable I want the options for the end users to have a PRIN DIAG field (prev loaded), a SEC DIAG field (prev loaded), and then a DIAGNOSIS field which is combo of both. To load my script pre-crosstable it used about 4 gigs of ram. When I added the 3 crosstables I killed it after it had consumed close to 9 gigs of ram. Just wondering if someone can verify I am using the best practice? Attached is the full script (crosstables are pg. 4-5). 

Thank you,

EK


CrossTable (ALLDIAG, DIAGNOISIS,2) 
LOAD
[PRIN DIAG],
[SEC DIAG & NAME]
Resident FINAL_DATA_1;

CrossTable (ALLPROC, PROCEDURE, 3)
LOAD
[PRIN PROC],
[SEC PROC ICD9 & NAME],
[SEC PROC HCPC & NAME]
Resident FINAL_DATA_1;

CrossTable (ALLPHYS, PHYSICIAN, 4)
LOAD
ATTENDING,
ADMITTING,
REFERRING,
SURGEON
Resident FINAL_DATA_1;


Drop table FINAL_DATA_1;

0 Replies