2022.10.25 09:35 AM
2022.10.25 11:19 PM
Hi araza,
At 3.5, it's still limited to a 32-bit space (so 2^32 worth).
From 3.6, it's 64-bit, see https://code.kx.com/q/releases/ChangesIn3.6/#nucs-not-upwardly-compatible
Curious what you're doing with the sym file though?
Large sym files in HDBs generally reload and write-down times, so it's generally not a good idea, eventually leading to a need for sym file compaction: https://code.kx.com/q/kb/compacting-hdb-sym/
Cheers,
Sean
2022.10.25 11:19 PM
Hi araza,
At 3.5, it's still limited to a 32-bit space (so 2^32 worth).
From 3.6, it's 64-bit, see https://code.kx.com/q/releases/ChangesIn3.6/#nucs-not-upwardly-compatible
Curious what you're doing with the sym file though?
Large sym files in HDBs generally reload and write-down times, so it's generally not a good idea, eventually leading to a need for sym file compaction: https://code.kx.com/q/kb/compacting-hdb-sym/
Cheers,
Sean
2022.10.26 08:14 AM
Hi Sean,
Appreciate your help!
We were monitoring our sym file, so just wondering what the hard limit on its size was. Definitely want to avoid doing a sym file compaction.
Thanks,
Abbas
EMEA
Tel: +44 (0)28 3025 2242
AMERICAS
Tel: +1 (212) 447 6700
APAC
Tel: +61 (0)2 9236 5700
KX. All Rights Reserved.
KX and kdb+ are registered trademarks of KX Systems, Inc., a subsidiary of FD Technologies plc.