12 The Sybase Wire Protocol Driver : Using DataDirect Bulk Load on Sybase

Using DataDirect Bulk Load on Sybase
DataDirect Bulk Load offers a simple, consistent way to do bulk load operations. See “Using DataDirect Bulk Load” for details.
For Sybase, some additional database configuration is required when the destination table for a bulk load operation does not have an index defined. If you are using a destination table that does not have an index defined, you can ask the database operator to execute the following commands:
use master
sp_dboption test, "select into/bulkcopy/pllsort", true
This option is required to perform operations that do not keep a complete record of the transaction in the log. For more information, refer to the Sybase documentation.
Alternatively, you can define an index on the destination table.
Failure to properly configure the database results in errors such as the following:
"You cannot run the non-logged version of bulk copy in this database. Please check with the DBO."
Bulk Copy Operations and Transactions
Sybase does not support a bulk insert within a transaction, and returns an error if a bulk copy operation is attempted in the scope of an existing transaction.
The Sybase server treats each batch of the bulk copy operation as a single transaction. If any rows in the batch are rejected, the entire transaction is rolled back.
Performance Considerations
Sybase defines two bulk copy modes, described in Table 12-4. Sybase automatically selects the appropriate mode at run time. For more information, refer to your Sybase documentation.
 
Destination Table Characteristics
The into/bulkcopy/pllsort dboption must be set to true.
Page allocations are logged, but row inserts are not
You must dump the database before backing up (dumping) the transaction log.
The transaction log can become very large. After the bulk copy completes, back up your database with dump database, then truncate the log with dump transaction.