Now the final inserted row counts should match the number of imported rows.

I created below table in Sybase ASE and then imported using the attached file. After import ADS displayed inserted 54 rows successfully, when I did a select * 0 rows was inserted. Hence, row count is incorrect

CREATE TABLE dbo.i9021  ( 

        a       varchar(25) NOT NULL,

        b       varchar(25) NOT NULL,

        c       varchar(25) NOT NULL,

        d       varchar(25) NOT NULL,

        CONSTRAINT s PRIMARY KEY CLUSTERED(a)

        WITH max_rows_per_page = 0, reservepagegap = 0

        )

LOCK ALLPAGES

GO

When an error occurs for Sybase BCP Import, preparedStmt.executeBatch() throws SQLException instead of BatchUpdateException.  Fixed the inserted count by checking preparedStmt.getUpdateCount() in this case.

One observation with Sybase BCP Import:

- For Sybase ASE, if one record in a batch of 500 fails, none of the record is inserted.

- For Sybase IQ with iAnywhere Driver, if one record in a batch of 500 fails, the other 499 records are still inserted.

With the same table and file, I attached, the final row count is 1 less than the original value. Can, you look into this in 14.0.0-beta-74 ?

I can reproduce the problem using batch import (not BCP import) and choose "first row contains column names" option.

Let's look at the first 10 lines of your data file.

When the "first row contains column names" option is checked, the first row is not considered as data.  It looks like 3 records get inserted, but BatchUpdateException.getUpdateCounts() returns 2 elements only.

f,g,h,i  <-- column names, not imported
j,k,l,m  <-- success
a,b,c,d  <-- success
j,k,l,m  <-- error, duplicate
a,b,c,d  <-- error, duplicate
f,g,h,i  <-- success (select query shows that this record gets inserted)
j,k,l,m
a,b,c,d
f,g,h,i
j,k,l,m

When the "first row contains column names" option is not checked, the first row is imported.  In this case, the first 3 records get inserted and BatchUpdateException.getUpdateCounts() returns 3 elements correctly.

f,g,h,i  <-- success
j,k,l,m  <-- success
a,b,c,d  <-- success
j,k,l,m  <-- error, duplicate
a,b,c,d  <-- error, duplicate
f,g,h,i  <-- error, duplicate
j,k,l,m
a,b,c,d
f,g,h,i
j,k,l,m

There is a bug with BatchUpdateException -- Sybase bug, not ours.