Load Table Statement - Sybase Adaptive Server Anywhere Reference

LOAD TABLE statement

LOAD TABLE statement
Function
Syntax
Permissions
Side effects
Description
560
Use this statement to import bulk data into a database table from an external
ASCII-format file. Inserts are not recorded in the log file, raising the risk
that data will be lost in the event of a crash and making this statement
unusable with SQL Remote or with MobiLink client databases.
LOAD [ INTO ] TABLE [ owner ]. table-name [( column-name , ... )]
FROM ' filename - string '
[ load-option ... ]
load-option :
CHECK CONSTRAINTS { ON | OFF }
| DEFAULTS { ON | OFF }
| DELIMITED BY string
| ESCAPE CHARACTER character
| ESCAPES { ON | OFF }
| FORMAT { ASCII | BCP }
| QUOTES { ON | OFF }
| STRIP { ON | OFF }
| WITH CHECKPOINT { ON | OFF }
The permissions required to execute a LOAD statement are set on the
database server command line, using the –gl command-line option.
$
For more information, see -gk command-line option.
Requires an exclusive lock on the table.
The table cannot be a declared local temporary table.
Inserts are not recorded in the log file. Thus, the inserted rows may not be
recovered in the event of a crash. In addition, the LOAD TABLE statement
should never be used in database involved in SQL Remote replication or
databases used as MobiLink clients because these technologies replicated
changes through analysis of the log file.
The LOAD TABLE statement does not fire triggers, including referential
integrity actions.
A COMMIT is automatically performed at the end of the load statement.
A checkpoint is carried out at the beginning of the operation. A second
checkpoint, at the end of the operation, is optional.
The LOAD TABLE statement allows efficient mass insertion into a database
table from an ASCII file. LOAD TABLE is more efficient than the
Interactive SQL statement INPUT.
LOAD TABLE places an exclusive lock on the whole table; it does not fire
any triggers associated with the table.