Constructing a Batch Import File

A Batch Import file may include many transactions to import many files of the same or different types, as necessary. A complete transaction must be defined for each file being imported. Collectively, the batch commands for a given transaction are a set of parameters that describe the source file and the destination table.

Perhaps the easiest way to construct a Batch Import file containing multiple imports is to let SQLWizard create the batch commands for you. For each file you want to include in your Batch Import file, fill in the required information on an Import window. Then use the Save As command from the File menu to save the Batch Import specifications. After you have created these individual Batch Import files, use any text editor to copy and paste all of the batch commands into one file. Add comments as desired.

When constructing a Batch Import file, keep in mind the following:

• Each transaction in a Batch Import file must begin with a name or label in square brackets to separate each set of batch commands. For example, you might want to enter the name of the table to identify the transaction, such as [EmployeeTable].
• Each Batch Import command must end with a semicolon (;).
• You may include spaces and blank lines as needed to improve readability. The spaces and blank lines are ignored by SQLWizard.
• C-style comments can be used in the specifications. For example: /* comment */.
• All commands are case-insensitive. You may use any combination of upper and lower case letters (for example, INSERT_MODE is the same as Insert_Mode).

Not all Batch Import commands are required for all file types. For instance, the field and record delimiter (FLD_DELIMITER and REC_DELIMITER, respectively) commands are required only for importing delimited, free-format ASCII files. Likewise, the OFFSETS command is required only for importing from columnar, fixed-format ASCII files.