Fast bcp

Adaptive Server uses fast bcp in certain situations.

The SAP ASE server uses fast bcp when (in all cases sp_dboption 'select into/bulkcopy/pllsort' is enabled and the table does not have a unique clustered index):
  • You do not explicitly specify fast-logged bcp.

  • The table has a non-unique, nonclustered index. The SAP ASE server logs the index updates and the page allocations only. It does not log inserts into the table.

  • A table has triggers. However, bcp does not fire any triggers in the target table.

  • A table has datarows or datapage locking scheme with a unique clustered index.

If the table includes nonclustered indexes or triggers, but sp_dboption 'select into/bulkcopy/pllsort' is not enabled, the SAP ASE server uses slow bcp.

Fast bcp runs more slowly while a dump database is taking place.

Fast bcp logs only the page allocations. For copying data in, bcp is fastest if your database table has no indexes.

If you use fast bcp to make data inserts, which fast bcp does not log, you cannot back up (dump) the transaction log to a device. The changes are not in the log, and a restore cannot recover nonexistent backup data. The requested backup (dump transaction) produces an error message that instructs you to use dump database instead. This restriction remains in force until a dump database successfully completes. For more information about dump database and dump transaction, see the System Administration Guide, and the Reference Manual.

bcp optimization is performed by the SAP ASE server and does not require that you use Open Client version 15.0 or later.