With temporary table, you work on client system.
So if you insert many records in this table, you consummate much memory on client and insert will be speedless.
To test performance loop through the items andinsert them into a temporary item record. Mostly there is very little performace hit, and the amount of memory depends on number of records inserted.
Ahmed Rashed Amini
Independent Consultant/Developer
That topic isn't displaying correctly (at least for me this morning), so I'll repeat here the more interesting parts:
Navision 3.10/3.60/3.70 will allocate up to 300K for each temp table - the allocation will begin when the first INSERT occurs and continue up to that limit as inserts/modifications are made - the remainder of the storage occupied by the temp table is written to disk in a temp file so you will see no significant memory usage for a temp table. None of this space is freed until the table handle is out of scope so deleting records in a temp table does not reduce this memory nor the size of the temp file.
In Attain 3.01 this threshold was 30K, from Navision 4.0 it is 500k.
The up-side is that you can have almost as many records as you want (<2.6billion) in your temp table without worrying about memory issues inc. swapping - and without a performance problem since they are b-trees.
Comments
With temporary table, you work on client system.
So if you insert many records in this table, you consummate much memory on client and insert will be speedless.
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
http://www.mbsonline.org/forum/topic.asp?TOPIC_ID=11163
That topic isn't displaying correctly (at least for me this morning), so I'll repeat here the more interesting parts:
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!