|
See Also
Export existing data only to
import it again in a different form. The data can be transformed or
processed either externally using another tool, or by USoft Batch
during import.
Often an alternative for
export-for-import, is to use a USoft Batch SQL task.
There are a number of reasons
why export-for-import might be called for:
|
·
|
You want to use third-party facilities on the data, such as an
operating system script, or a database vendor tool. |
|
·
|
You want to be able to process and commit records one-by-one.
For example, using import task set virtuals for computed
columns. |
|
·
|
You want to use USoft Batch-specific features on the data. For
example, default status files, constraint deactivation. |
How to export-for-import:
| 1.
|
Write an export task selecting all data concerned. If you use
an ORDER BY clause, you can take advantage of the record order in
the resulting external file when you write the import task. |
| 2.
|
Process the resulting external file, if the aim of
export-for-import was to be able to apply tools other than USoft
Batch to the data. |
| 3.
|
Import the external file: |
|
·
|
Set RECORD level commit if the aim of export-for-import was to
achieve record-level commit. |
|
·
|
Use status files, status fields, job parameters, import task
set virtuals, constraint deactivation etc., if the aim of
export-for-import was to benefit from USoft Batch import
facilities. |
|
