Microsoft KB Archive/80633

{|
 * width="100%"|

The information in this article applies to:
 * Microsoft SQL Server version 4.2 for OS/2

BUG# 1222 (4.2)

SYMPTOMS
When the bulk copy program (BCP) is used to insert data into a SQL Server table, the insertion of the rows is logged in the transaction log, even though no indexes are present on the destination table.

CAUSE
The &quot;fast&quot; (or &quot;non-logged&quot;) version of BCP should be used if the table into which the data is being inserted does not contain any indexes. However, if the table contains any kind of a trigger (INSERT, UPDATE, or DELETE trigger), the insertion of the rows from BCP will be logged. The presence of a trigger on the table will only cause the inserts to be logged; the trigger will not be fired.

WORKAROUND
To work around this problem, drop any triggers that are defined on that table before using BCP. When the BCP is complete, re-create the trigger(s).

STATUS
Microsoft has confirmed this to be a problem in SQL Server version 4.2. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
 * }

-

Last reviewed: April 28, 1997

© 1998 Microsoft Corporation. All rights reserved. Terms of Use.