Reject tables

Previous Next

Instead of having USoft Batch produce import status files, you can use the database for import error handling. Several strategies exist:

Have a default error file made, then import the error file into a "reject table". A reject table corresponds to one application table. Its purpose is to accept records that for some reason could not be imported into the application table.

Import all records into a reject table, then have USoft Batch transfer records from this table into the actual application table where possible. After this operation, the contents of the reject table can be read as an error report.

Import expected error data into a reject table, deal with this data separately, then import all data into the application table.

Depending on the strategy chosen, general advantages of storing import errors are:

1.You do not need to maintain import status files. If you disable their creation, performance is improved.
2.Error reports that are stored in the database (as opposed to files) can be:

Made more readable

Queried using any desired ad-hoc query

Made to contain any desired additional information

Easily processed further, using SQL.

See also

Defining a Reject Table

Transferring Error Status Data Into a Reject Table

Importing All Records Via a Reject Table

Detecting and Repairing Expected Import Errors Before Bulk Import