USEDISK FLUSH performs the same operation in the same way as USEDISK, except the end-result table is
saved to a single (flushed) table that is then consolidated when SAVE is called at the end of the Import Script.


IMPORT table=USEDISK FLUSH a1.table1

Note: Tables are not available for Querying, Updates or Deletes with the FLUSH variant.

By using USEDISK FLUSH, it is possible to generate larger extract files using a lot less memory as it only needs to be able to contain one column of information at a time. Extraction times will take about 5-10% longer. Do not use USEDISK FLUSH if this table needs to be referenced in a later part of the import script.

Sufficient storage is required during the import phase for an extra copy of this table (on the disk in which the targitdb file is being saved).

Was this article helpful?
0 out of 0 found this helpful



Please sign in to leave a comment.