Slow bcp

In certain situations, use slow bcp.

Use slow bcp when:
  • sp_dboption 'select into/bulkcopy/pllsort' is off.

  • sp_dboption 'select into/bulkcopy/pllsort' is on, but the table uses the allpages locking scheme and has a clustered index.

  • sp_dboption 'select into/bulkcopy/pllsort' is on, but the table has a unique nonclustered index.

    If the option ignore_dup_key option is enabled on the unique index, performing fast bcp can put the table and index in an inconsistent state if rows with duplicate keys are inserted. To avoid the inconsistency, the SAP ASE server performs slow bcp.

  • If the table has nonclustered indexes or triggers, and the table is marked for replication or the database is used as a warm standby.

    Because fast bcp does not log inserts, if the SAP ASE server uses fast bcp, the rows bcp copies cannot be recovered on the replication site if there is a problem. The SAP ASE server uses slow bcp in these situations to maintain compatibility with applications that were written to use the old behavior.