The following Help topic discusses the dbsrv12 -b bulk loading option.

It says "You can also use some of the logging options available for the LOAD TABLE statement that allow bulk-loaded data to be recorded in the transaction log."

Does that mean LOAD TABLE WITH ROW LOGGING will actually override dbsrv12 -b and cause data to be written to the transaction log?

http://dcx.sybase.com/index.html#1200en/dbusage/load-s-5991168.html

Data recovery issues for bulk operations

You can run the database server in bulk operations mode (the -b server option). When you use this option, the database server does not perform certain important functions. Specifically:

Function Implication
Maintain a transaction log There is no record of the changes. Each COMMIT causes a checkpoint.
Lock any records There are no serious implications.

Alternatively, you may also need to ensure that data from bulk loading is still available in the event of recovery. You can do so by keeping the original data sources intact, and in their original location. You can also use some of the logging options available for the LOAD TABLE statement that allow bulk-loaded data to be recorded in the transaction log. See LOAD TABLE statement.

Caution You should back up the database before and after using bulk operations mode because your database is not protected against media failure in this mode.